public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102831] [12 regression] Spurious -Wparentheses etc. warnings
Date: Mon, 08 Nov 2021 10:12:09 +0000	[thread overview]
Message-ID: <bug-102831-4-g6Sm6RYd84@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102831-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102831

--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #2 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
> Are you guys able to reliably reproduce the problem?  Asking because for me, it
> was very flaky: some (seemingly random) change elsewhere in the compiler, and
> PR101574 often didn't reproduce anymore (but came back later).  (But really
> have not anymore seen it since the aforementioned commit.)

In my case the errors were anything but reliable: they started to show on
Solaris 11.3 builds only, sometimes sparc, sometimes x86, at others
(from the identical source tree) Solaris 11.4/SPARC only.

In the end (not having made progress to figure out what's wrong), I
ended  up with a local patch to disable -Wparentheses for
lra-constraints.c and sparseset.c as those failures didn't have any
other effect on the build or testsuite results, but just had become a
nuisance.

  parent reply	other threads:[~2021-11-08 10:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  9:38 [Bug bootstrap/102831] New: " ro at gcc dot gnu.org
2021-10-19  9:38 ` [Bug bootstrap/102831] " ro at gcc dot gnu.org
2021-11-08  8:13 ` ebotcazou at gcc dot gnu.org
2021-11-08 10:00 ` tschwinge at gcc dot gnu.org
2021-11-08 10:12 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2021-11-08 15:42 ` msebor at gcc dot gnu.org
2021-11-08 22:58 ` bergner at gcc dot gnu.org
2021-11-08 23:11 ` bergner at gcc dot gnu.org
2021-11-09  2:32 ` msebor at gcc dot gnu.org
2021-11-09 17:19 ` bergner at gcc dot gnu.org
2022-01-17 18:22 ` tschwinge at gcc dot gnu.org
2022-03-10 10:19 ` rguenth at gcc dot gnu.org
2022-03-10 10:26 ` ro at CeBiTec dot Uni-Bielefeld.DE

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=bug-102831-4-g6Sm6RYd84@http.gcc.gnu.org/bugzilla/ \
    --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: 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).