bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/4013] New: Add GAS option for .code16gcc and postfix text/


From: etienne_lorrain at yahoo dot fr
Subject: [Bug binutils/4013] New: Add GAS option for .code16gcc and postfix text/data/rodata/bss ?
Date: 9 Feb 2007 09:53:25 -0000

In the enhancement section, it "would be nice" to have an option
which does the same as inserting ".code16gcc" as first line of
the assembler file.
 I see "Target i386 options" -32 and -64 already defined, maybe
the -16 / -16gcc could be used for ".code16" and ".code16gcc",
or simply -16 for ".code16gcc" if it is simpler for that parameter
to be a number (GCC calling automatically the assembler with
temporary generated file).

 In the same kind of application, it "would be nice" to have a
parameter definning a string (by default empty) to postfix section
used when (the compiler) uses .text, .data, .rodata, .bss to
create section. For instance, gas --postfix-section="16" would process
.text  --> to create section  --> .section .text16
.data  --> to create section  --> .section .data16
.bss   --> to create section  --> .section .bss16
.rodata  --> to create section  --> .section .rodata16

 That would help application like the GPL bootloader Gujin (at
http//gujin.org ).

 Thanks for your attention,
 Etienne.

-- 
           Summary: Add GAS option for .code16gcc and postfix
                    text/data/rodata/bss ?
           Product: binutils
           Version: 2.18 (HEAD)
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: binutils
        AssignedTo: unassigned at sources dot redhat dot com
        ReportedBy: etienne_lorrain at yahoo dot fr
                CC: bug-binutils at gnu dot org
 GCC build triplet: i386-redhat-linux
  GCC host triplet: i386-redhat-linux
GCC target triplet: i386-redhat-linux


http://sourceware.org/bugzilla/show_bug.cgi?id=4013

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]