This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC 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] | |
On Tue, Jan 14, 2003 at 08:03:01AM +0100, Robert Schiele wrote: > Thanks. With your crtbegin.o it also works for me. So I will try to > build a gcc 3.2 with binutils 2.12.x.x.x to check whether it makes a > difference which binutils are used to build the compiler. Well, I got the switch that triggers it: HAVE_LD_EH_FRAME_HDR If this Macro was defined, the crtbegin code cannot handle the situation I described in the bug report. Without it can handle the situation quite sane. This is the case with _all_ compilers since 3.2 release. (I haven't an older one at hand to test.) Obviously this switched is on if you used binutils 2.12.x.x.x at configure time as they support this feature, but 2.11.x.x.x do not and such it is turned off there. So it is perfectly clear now, why you couldn't reproduce the problem. This means the problem obviously is in the crtstuff code that handles eh_frame_hdr stuff. So we need some binutils gurus here. Robert -- Robert Schiele Tel.: +49-621-181-2517 Dipl.-Wirtsch.informatiker mailto:rschiele@uni-mannheim.de
Attachment:
msg00881/pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |