public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/27781] [4.1/4.2 Regression] weak-attribute over-optimisation Date: Sun, 28 May 2006 15:23:00 -0000 [thread overview] Message-ID: <20060528152312.12431.qmail@sourceware.org> (raw) In-Reply-To: <bug-27781-12747@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from pinskia at gcc dot gnu dot org 2006-05-28 15:23 ------- Actually no, you have to use -fPIC to get this not to be optimized, otherwise func will be bound locally which is not what you want. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Component|c |middle-end http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27781
next prev parent reply other threads:[~2006-05-28 15:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-28 9:39 [Bug c/27781] New: weak-attribute over-optimisation with 4.1 jan dot kiszka at web dot de 2006-05-28 12:04 ` [Bug c/27781] [4.1/4.2 Regression] weak-attribute over-optimisation rguenth at gcc dot gnu dot org 2006-05-28 14:00 ` rguenth at gcc dot gnu dot org 2006-05-28 15:23 ` pinskia at gcc dot gnu dot org [this message] 2006-06-01 18:36 ` [Bug middle-end/27781] " trini at kernel dot crashing dot org 2006-06-04 19:32 ` mmitchel at gcc dot gnu dot org 2006-06-15 15:54 ` patchapp at dberlin dot org 2006-06-15 17:30 ` rguenth at gcc dot gnu dot org 2006-06-15 17:39 ` [Bug middle-end/27781] [4.1 " rguenth at gcc dot gnu dot org 2006-06-16 17:53 ` pinskia at gcc dot gnu dot org 2006-06-21 15:36 ` rguenth at gcc dot gnu dot org 2006-06-21 15:43 ` rguenth 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=20060528152312.12431.qmail@sourceware.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).