From: Jan Hubicka <hubicka@ucw.cz>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gcc@gcc.gnu.org, Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org
Subject: Re: Detect EAF flags in ipa-modref
Date: Sun, 15 Nov 2020 12:12:54 +0100 [thread overview]
Message-ID: <20201115111254.GB45304@kam.mff.cuni.cz> (raw)
In-Reply-To: <87361ahph7.fsf@linux-m68k.org>
> This breaks bootstrap with go.
>
> ../../gcc/go/gofrontend/go-diagnostics.cc: In function 'std::string expand_message(const char*, va_list)':
> ../../gcc/go/gofrontend/go-diagnostics.cc:110:61: error: '<anonymous>' may be used uninitialized [-Werror=maybe-uninitialized]
> 110 | "memory allocation failed in vasprintf");
> | ^
Well, this may be simply a false positive (except that the warning is
clearly mislocalted and cryptic) I was bootstrapping with go just few
minutes ago, so I wonder what configure flags you use?
Honza
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
> "And now for something completely different."
next prev parent reply other threads:[~2020-11-15 11:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 12:47 Definition of EAF_NOESCAPE and fnspec strings Jan Hubicka
2020-11-09 7:31 ` Richard Biener
2020-11-09 10:29 ` Jan Hubicka
2020-11-09 12:38 ` Richard Biener
2020-11-09 13:16 ` Detect EAF flags in ipa-modref Jan Hubicka
2020-11-09 23:14 ` Jan Hubicka
2020-11-10 9:17 ` Jan Hubicka
2020-11-10 10:25 ` Jan Hubicka
2020-11-10 10:55 ` Jan Hubicka
2020-11-10 11:04 ` Richard Biener
2020-11-10 12:54 ` Jan Hubicka
2020-11-10 14:31 ` Jan Hubicka
2020-11-13 8:06 ` Richard Biener
2020-11-15 13:25 ` H.J. Lu
2020-11-15 14:13 ` Jan Hubicka
2020-11-15 10:41 ` Andreas Schwab
2020-11-15 11:12 ` Jan Hubicka [this message]
2020-11-15 11:25 ` Rainer Orth
2020-11-15 12:33 ` Jan Hubicka
2020-11-15 12:43 ` Rainer Orth
2020-11-15 13:03 ` Jan Hubicka
2020-11-15 16:03 ` Rainer Orth
2020-11-15 16:15 ` Andreas Schwab
2020-11-15 18:07 ` Jan Hubicka
2020-11-16 7:48 ` Richard Biener
2020-11-16 9:26 ` Andreas Schwab
2020-11-16 10:59 ` Jan Hubicka
2020-11-16 12:36 ` Richard Biener
2020-11-16 12:44 ` Jan Hubicka
2020-11-16 19:33 ` Martin Liška
2020-11-16 19:46 ` Jan Hubicka
2020-11-11 10:09 ` Richard Biener
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=20201115111254.GB45304@kam.mff.cuni.cz \
--to=hubicka@ucw.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=schwab@linux-m68k.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: 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).