public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aj at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/11669] New: [3.4 regression] Calling of static functions does not work (build of glibc broken) Date: Fri, 25 Jul 2003 09:11:00 -0000 [thread overview] Message-ID: <20030725091122.11669.aj@gcc.gnu.org> (raw) PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11669 Summary: [3.4 regression] Calling of static functions does not work (build of glibc broken) Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: critical Priority: P3 Component: other AssignedTo: geoffk at gcc dot gnu dot org ReportedBy: aj at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-linux-gnu GCC host triplet: i686-linux-gnu GCC target triplet: i686-linux-gnu This is a testcase reduced from a failure to compile glibc on i686-linux-gnu with current GCC: gromit:~/tmp:[0]$ /opt/gcc/3.4-devel/bin/gcc -c test-failure.c -O2 gromit:~/tmp:[0]$ nm test-failure.o 00000010 T call_fixup 00000000 t fixup gromit:~/tmp:[0]$ /opt/gcc/3.4-devel/bin/gcc -c test-failure.c -O2 -DUSE_DECLARATION gromit:~/tmp:[0]$ nm test-failure.o 00000010 T call_fixup U fixup 00000000 t fixup.0 The fixup.0 declaration is wrong here. I suspect the IMI patches and assigned it therefore to Geoff Keating. To reproduce use the simple follwing simple code snippet: #if USE_DECLARATION /* Removing the prototype makes this work. */ static int fixup (int i) __attribute__ ((used)); #endif static int __attribute__ ((__used__)) fixup (int i) { return i+1; } int call_fixup (void) { asm ("call fixup\n\t"); return 0; }
next reply other threads:[~2003-07-25 9:11 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-25 9:11 aj at gcc dot gnu dot org [this message] 2003-07-25 11:24 ` [Bug other/11669] " pinskia at physics dot uc dot edu 2003-07-25 12:53 ` pinskia at physics dot uc dot edu 2003-07-25 14:44 ` schwab at suse dot de 2003-07-25 14:50 ` pinskia at physics dot uc dot edu 2003-07-26 0:21 ` drow at mvista dot com 2003-07-26 5:27 ` aj at gcc dot gnu dot org 2003-07-26 10:16 ` geoffk at gcc dot gnu dot org 2003-07-26 16:17 ` mec at shout dot net 2003-07-26 17:07 ` mec at shout dot net 2003-07-26 18:37 ` geoffk at gcc dot gnu dot 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=20030725091122.11669.aj@gcc.gnu.org \ --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).