Thanks for all the help. I have tried a few things now and decided to
try and create a new section called .edoc I tried using .comment on my
machine, however there is already data in .comment on my machine and
it will make parsing the data from the section to find my data a
little more difficult as
On Oct 3, 2006, at 5:43 PM, Brendon Costa wrote:
I think I could insert my data into the .s file into a particular
section. I am not sure if I should create my own named section
I'd recommend .comment probably. If you want to productize it, add
your own, and put it into your linker script.
Brendon Costa wrote:
> Mike Stump wrote:
>> Hum, on second thought, why not just encode the information you want
>> into the .o file. Just put it into a special section, in whatever
>> format you like, the linker will combine them, no additional files, .a
>> files work, ld -r foo.o bar.o -o new.o
Mike Stump wrote:
> Hum, on second thought, why not just encode the information you want
> into the .o file. Just put it into a special section, in whatever
> format you like, the linker will combine them, no additional files, .a
> files work, ld -r foo.o bar.o -o new.o works and so on. You can t
On Oct 2, 2006, at 9:24 PM, Brendon Costa wrote:
* Modify the ASM spec used for compiling .s files into .o files so
that it will somehow rename the /tmp/foo1.s.edc files to
/tmp/gah1.o.edc files where /tmp/gah1.o is the name of the output .o
file that comes from the assembler.
* Write a wrapp
Ian Lance Taylor wrote:
> Brendon Costa <[EMAIL PROTECTED]> writes:
>
>> Then GCC (SOMEWHERE I CANT SEEM TO FIND THIS PART OF THE CODE) links
>> these objects by calling ld with /tmp/foo1.o and /tmp/foo2.o combining
>> these into: blah
>
> It's done in the driver, gcc.c. Look for link_command_sp
On Oct 2, 2006, at 5:40 PM, Brendon Costa wrote:
Now I currently need to generate an associated file for each of these
files as well.
Additionally, see -save-temps for additional hints. This avoids /tmp/
temp234.s as an intermediate file and generates ext_test.s instead.
Run with -v, and y
Brendon Costa <[EMAIL PROTECTED]> writes:
> Then GCC (SOMEWHERE I CANT SEEM TO FIND THIS PART OF THE CODE) links
> these objects by calling ld with /tmp/foo1.o and /tmp/foo2.o combining
> these into: blah
It's done in the driver, gcc.c. Look for link_command_spec.
Ian
