From: Richard Henderson <rth@redhat.com>
To: "Joseph S. Myers" <jsm@polyomino.org.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: Undefined static functions
Date: Tue, 31 Aug 2004 20:44:00 -0000 [thread overview]
Message-ID: <20040831203323.GA8419@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0408310828390.19517@digraph.polyomino.org.uk>
On Tue, Aug 31, 2004 at 08:31:09AM +0000, Joseph S. Myers wrote:
> This does rather make me wonder whether what check_global_declarations
> does after warning,
>
> /* This symbol is effectively an "extern" declaration now. */
> TREE_PUBLIC (decl) = 1;
>
> is particularly safe.
Doesn't sound like it. I guess the reason it works is that
encode_section_info has already done its job, and we don't
call back into it now.
> ... defining TREE_NO_WARNING to apply
> to decls as well as expressions looks safer.
TREE_NO_WARNING *does* apply to decls. See warn_uninit in tree-ssa.c.
r~
next prev parent reply other threads:[~2004-08-31 20:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 0:28 Joseph S. Myers
2004-08-31 6:02 ` Richard Henderson
2004-08-31 9:11 ` Joseph S. Myers
2004-08-31 20:44 ` Richard Henderson [this message]
2004-08-31 20:56 ` Joseph S. Myers
2004-09-01 22:24 ` Richard Henderson
2004-08-31 23:55 ` Mark Mitchell
2004-09-01 0:10 ` Joseph S. Myers
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=20040831203323.GA8419@redhat.com \
--to=rth@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm@polyomino.org.uk \
/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: link
Be 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).