public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10047: [3.3 regression] -fno-default-inline produces bogous warnings Date: Sat, 22 Mar 2003 21:36:00 -0000 [thread overview] Message-ID: <20030322213600.5046.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10047; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: gcc-gnats@gcc.gnu.org, rguenth@tat.physik.uni-tuebingen.de, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org, nathan@codesourcery.com Cc: Subject: Re: c++/10047: [3.3 regression] -fno-default-inline produces bogous warnings Date: Sat, 22 Mar 2003 13:39:00 -0800 The regression appeared with this patch to mainline and 3.3-branch (cp directory): 2002-12-26 Nathan Sidwell <nathan@codesourcery.com> PR c++/4803 * decl2.c (mark_used): Defer inline functions. (finish_file): Merge deferred_fns loops. Check all used inline functions have a definition. * method.c (make_thunk): Thunks are not inline. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10047
next reply other threads:[~2003-03-22 21:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-22 21:36 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-18 16:16 steven 2003-03-12 20:06 rguenth
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=20030322213600.5046.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).