public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "moonshine at kapsi dot fi" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/44802] New: -flto -fuse-linker-plugin causes undefined references from libc in the link phase Date: Sat, 03 Jul 2010 12:31:00 -0000 [thread overview] Message-ID: <bug-44802-19380@http.gcc.gnu.org/bugzilla/> (raw) This works fine without -fuse-linker-plugin (with all object files extracted from archive). This reduced testcase has some undefined references of its own but still exposes the bug as shown below. Whole output of linking a complete program is attached because of its 30 kB size. Also a preprocessed source file is attached. gcc -std=gnu99 -fvisibility=hidden -O3 -fomit-frame-pointer -march=pentium4 -flto -fuse-linker-plugin -o xz main.i --SNAP-- /home/misty/gcc/lib/gcc/i686-pc-linux-gnu/4.5.1/../../../../i686-pc-linux-gnu/bin/ld: error: hidden symbol 'fgetc' is not defined locally /home/misty/gcc/lib/gcc/i686-pc-linux-gnu/4.5.1/../../../../i686-pc-linux-gnu/bin/ld: error: hidden symbol 'ferror' is not defined locally --SNAP-- main.i was produced with: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../.. -DLOCALEDIR=\"/home/misty/gcc/share/locale\" -I../../src/common -I../../src/liblzma/api -I../../lib -DLZMA_API_STATIC -pthread -fvisibility=hidden -Wall -Wextra -Wformat=2 -Winit-self -Wmissing-include-dirs -Wstrict-aliasing -Wfloat-equal -Wundef -Wshadow -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wlogical-op -Waggregate-return -Wstrict-prototypes -Wold-style-definition -Wmissing-prototypes -Wmissing-declarations -Wmissing-noreturn -Wredundant-decls -O3 -fomit-frame-pointer -march=pentium4 -flto -fuse-linker-plugin -MT xz-main.o -MD -MP -MF .deps/xz-main.Tpo -E main.c >main.i -- Summary: -flto -fuse-linker-plugin causes undefined references from libc in the link phase Product: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: moonshine at kapsi dot fi GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44802
next reply other threads:[~2010-07-03 12:31 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-03 12:31 moonshine at kapsi dot fi [this message] 2010-07-03 12:32 ` [Bug lto/44802] " moonshine at kapsi dot fi 2010-07-03 12:33 ` moonshine at kapsi dot fi 2010-07-03 13:35 ` moonshine at kapsi dot fi 2010-07-08 2:03 ` moonshine at kapsi dot fi 2010-07-26 21:14 ` hubicka at gcc dot gnu dot org 2010-07-27 12:42 ` moonshine at kapsi dot fi
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-44802-19380@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).