This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Java broken after i386 PIC change
- To: apbianco at cygnus dot com, rth at redhat dot com, gcc-bugs at gcc dot gnu dot org
- Subject: Java broken after i386 PIC change
- From: Bryce McKinlay <bryce at albatross dot co dot nz>
- Date: Fri, 19 Jan 2001 00:02:57 +1300
- CC: martin dot kahlert at infineon dot com, java-discuss at sourceware dot cygnus dot com
- References: <20010116123822.A16053@keksy.muc.infineon.com> <3A6675A9.745842BC@albatross.co.nz> <14950.34116.664233.394672@deliverance.cygnus.com>
Richard,
> 2001-01-15 Richard Henderson
>
> * config/i386/i386.c (asm_output_function_prefix): Remove.
> (ix86_asm_file_end): New.
> (load_pic_register): Generate pic_label_name into a
> staticly allocated buffer.
> * config/i386/i386-protos.h: Update.
> * config/i386/i386.h (ASM_OUTPUT_FUNCTION_PREFIX): Remove.
> (ASM_FILE_END): New.
> * config/i386/i386afe.h: New file.
> * config.gcc (i?86-*-elf) [tm_file]: Use it.
> (i?86-*-{freebsd,linux*,moss*}): Likewise.
> * config/elfos.h (ASM_FILE_END): Undef before redefinition.
> * config/i386/cygwin.h (ASM_FILE_END): Likewise.
> * config/i386/osfrose.h (ASM_FILE_END): Invoke ix86_asm_file_end.
> * config/i386/sco5.h (ASM_FILE_END): Likewise.
> * config/i386/winnt.c (i386_pe_asm_file_end): Likewise.
>
This patch broke Java.
Before:
$ ./hello
Liberté, égalité, fraternité !
After:
$ ./hello
Segmentation fault (core dumped)
(gdb) bt
#0 0x0 in ?? ()
#1 0x804a8fe in __register_frame_info (begin=0x405818ec, ob=0x40583320)
at ../../gcc/frame-dwarf2.c:563
#2 0x404848c0 in __libc_global_ctors () at soinit.c:56
#3 0x40484942 in init (argc=1, argv=0xbffffa3c, envp=0xbffffa44)
at ../sysdeps/unix/sysv/linux/init-first.c:103
#4 0x4000d2dd in _dl_init (main_map=0x40015fd8, argc=1, argv=0xbffffa3c,
env=0xbffffa44) at dl-init.c:111
regards
[ bryce ]
Alexandre Petit-Bianco wrote:
> Bryce McKinlay writes:
>
> > I'm trying to track this down. Does anyone have any clues as to when
> > it broke and/or what might be causing this?
>
> I would say it happened over the week-end. I'm pretty sure I did an
> up-to-date build last Friday.