This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: bfd is broken


On Fri, Jan 11, 2002 at 12:38:45PM -0500, Jakub Jelinek wrote:
> On Fri, Jan 11, 2002 at 09:34:15AM -0800, H . J . Lu wrote:
> > I tried. I couldn't get gcsec-1.c to fail on Linux/x86. I am wondering
> > how it failed for him.
> 
> Executing on host: /usr/src/gcc/obj/gcc/xgcc -B/usr/src/gcc/obj/gcc/ /usr/src/gcc/gcc/testsuite/gcc.dg/special/gcsec-1.c  -ffunction-sections -fdata-sections -Wl,--gc-sections -static   -lm   -o ./a.out    (timeout = 300)
> collect2: ld terminated with signal 11 [Segmentation fault], core dumped
> compiler exited with status 1
> 
> > > I was looking for a testcase where it failed for you, so if you think the
> > > above is what happens, no further need for it (though it should probably
> > > be added as a testcase for ld).
> > 
> > I will see what I can do. I may write one which only runs on Linux/x86.
> > It should be good enough for catching breakage.
> 
> Well, there are 3 ways how to write it.
> Either write a plain C testcase which will test SHF_MERGE only if gcc
> supports it, or gcc -S and sed the .s file to make plain .rodata sections
> .section ".rodata.str", "aMS", @progbits, 1
> or have testcase fully in assembly (in which case it will be for one arch
> only).

I have a testcase in assembly. But it is quite tricky. You have to
use as from 2.11.92.0.12.3 to see the failure. I don't know how useful
the testcase is.


H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]