public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at transmeta dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/13842] [3.3 Regression] static inline emitted when not used Date: Sat, 24 Jan 2004 02:13:00 -0000 [thread overview] Message-ID: <20040124021352.27371.qmail@sources.redhat.com> (raw) In-Reply-To: <20040124014837.13842.dje@transmeta.com> ------- Additional Comments From dje at transmeta dot com 2004-01-24 02:13 ------- (In reply to comment #1) > Confirmed but a very minor regression because it is okay to emit something when it is not > referenced anyways, just 3.4 does a better job at checking if it is used or not. Don't forget that it's not just `foo' but also the undefined reference to `bar'. Link failures are occuring that didn't occur before. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13842
next prev parent reply other threads:[~2004-01-24 2:13 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-24 1:48 [Bug c/13842] New: static inline erroneously emitted dje at transmeta dot com 2004-01-24 2:03 ` [Bug c/13842] [3.3 Regression] " pinskia at gcc dot gnu dot org 2004-01-24 2:13 ` dje at transmeta dot com [this message] 2004-02-15 12:41 ` [Bug c/13842] [3.3 Regression] static inline emitted when not used gdr at gcc dot gnu dot org 2004-06-11 22:22 ` pinskia at gcc dot gnu dot org 2004-09-28 13:25 ` gdr at gcc dot gnu dot org 2004-09-28 13:29 ` pinskia at gcc dot gnu dot org 2004-09-28 13:53 ` gdr at cs dot tamu dot edu 2004-12-28 2:15 ` pinskia at gcc dot gnu dot org 2004-12-28 2:15 ` pinskia at gcc dot gnu dot org 2005-04-30 13:30 ` gdr at gcc dot gnu dot org 2005-04-30 14:32 ` gdr 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=20040124021352.27371.qmail@sources.redhat.com \ --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).