public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/46940] New: asm aliases with linker plugin segfaults Date: Tue, 14 Dec 2010 15:35:00 -0000 [thread overview] Message-ID: <bug-46940-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46940 Summary: asm aliases with linker plugin segfaults Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned@gcc.gnu.org ReportedBy: hubicka@gcc.gnu.org extern __attribute__((visibility("hidden"))) void _moz_foo (void); extern __typeof (_moz_foo) _moz_foo __asm__ ("" "INT__foo") __attribute__((__visibility__("hidden"))) ; void _moz_foo(void) { printf ("blah\n"); } extern __typeof (_moz_foo) EXT__foo __asm__("" "_moz_foo") __attribute__((__alias__("" "INT__foo"))); evans:/abuild/jh/trunk-3/build-inst2/gcc/:[0]# more t2.c extern void _moz_foo (void); main() { _moz_foo (); } evans:/abuild/jh/trunk-3/build-inst2/gcc/:[0]# ./xgcc -B ./ -O2 -flto t.c t2.c -fuse-linker-plugin t.c: In function ?_moz_foo?: t.c:5:3: warning: incompatible implicit declaration of built-in function ?printf? [enabled by default] lto1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://gcc.gnu.org/bugs.html> for instructions. lto-wrapper: ./xgcc returned 1 exit status lto-wrapper failedcollect2: ld returned 1 exit status The problem here is that we get prevailing definition of _moz_foo to be alias that has no cgraph node (nor alias node) attached. Bah.
next reply other threads:[~2010-12-14 15:35 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-14 15:35 hubicka at gcc dot gnu.org [this message] 2010-12-14 16:21 ` [Bug lto/46940] " hubicka at gcc dot gnu.org 2010-12-14 23:22 ` hubicka at gcc dot gnu.org 2010-12-14 23:23 ` hubicka at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-46940-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).