public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/67030] New: [6 Regression] ARM bootstrap failure due to [-Werror=tautological-compare] Date: Mon, 27 Jul 2015 15:58:00 -0000 [thread overview] Message-ID: <bug-67030-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67030 Bug ID: 67030 Summary: [6 Regression] ARM bootstrap failure due to [-Werror=tautological-compare] Product: gcc Version: 6.0 Status: UNCONFIRMED Keywords: build Severity: normal Priority: P3 Component: bootstrap Assignee: unassigned at gcc dot gnu.org Reporter: ktkachov at gcc dot gnu.org CC: mpolacek at gcc dot gnu.org Target Milestone: --- Target: arm I'm getting a bootstrap failure in stage 2 on arm-none-linux-gnueabihf due to the new warning: $SRC/gcc/cfgexpand.c: In function 'long long int expand_one_var(tree, bool, bool)': $SRC/gcc/defaults.h:1156:55: error: self-comparison always evaluates to false [-Werror=tautological-compare] #define SUPPORTS_STACK_ALIGNMENT (MAX_STACK_ALIGNMENT > STACK_BOUNDARY) Seems we need to be a bit smarter when it comes to macro expansions?
next reply other threads:[~2015-07-27 15:58 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-07-27 15:58 ktkachov at gcc dot gnu.org [this message] 2015-07-27 16:05 ` [Bug bootstrap/67030] " mpolacek at gcc dot gnu.org 2015-07-27 16:08 ` ktkachov at gcc dot gnu.org 2015-07-27 16:43 ` ktkachov at gcc dot gnu.org 2015-07-27 16:51 ` mpolacek at gcc dot gnu.org 2015-07-27 16:51 ` mpolacek at gcc dot gnu.org 2015-07-27 17:01 ` ktkachov at gcc dot gnu.org 2015-07-27 17:09 ` mpolacek at gcc dot gnu.org 2015-07-27 17:31 ` vries at gcc dot gnu.org 2015-07-27 19:10 ` mpolacek at gcc dot gnu.org 2015-07-27 19:15 ` mpolacek at gcc dot gnu.org 2015-07-27 19:22 ` christian.joensson at gmail dot com 2015-07-27 19:37 ` mpolacek at gcc dot gnu.org 2015-07-27 19:42 ` christian.joensson at gmail dot com 2015-07-28 8:14 ` ktkachov at gcc dot gnu.org 2015-07-28 8:24 ` mpolacek at gcc dot gnu.org 2015-07-28 16:57 ` ktkachov at gcc dot gnu.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=bug-67030-4@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: 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).