linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Miroslav Benes <mbenes@suse.cz>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for May 21 (objtool warnings)
Date: Tue, 26 May 2020 09:01:13 -0500	[thread overview]
Message-ID: <20200526140113.ppjywpx7uir3vrlj@treble> (raw)
In-Reply-To: <alpine.LSU.2.21.2005251303430.24984@pobox.suse.cz>

On Mon, May 25, 2020 at 01:07:27PM +0200, Miroslav Benes wrote:
> > I'll try to find out which optimization does this, because it is a 
> > slightly different scenario than hiding __noreturn from the callees. 
> > Probably -fno-ipa-pure-const again.
> 
> And it is indeed -fno-ipa-pure-const again.

It still seems odd to me that GCC's dead end detection seems to break
with -fno-ipa-pure-const.  Do you know if these issues can be fixed on
the GCC side?

-- 
Josh


  reply	other threads:[~2020-05-26 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 14:12 linux-next: Tree for May 21 Stephen Rothwell
2020-05-21 15:09 ` Daniel Thompson
2020-05-22  2:34 ` linux-next: Tree for May 21 (objtool warnings) Randy Dunlap
2020-05-22 16:34   ` Josh Poimboeuf
2020-05-25 10:10   ` Miroslav Benes
2020-05-25 11:07     ` Miroslav Benes
2020-05-26 14:01       ` Josh Poimboeuf [this message]
2020-05-26 16:39         ` Miroslav Benes
2020-05-27  8:57           ` Martin Jambor
2020-05-27 15:09             ` Josh Poimboeuf
2020-05-25 18:04     ` Randy Dunlap

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=20200526140113.ppjywpx7uir3vrlj@treble \
    --to=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mbenes@suse.cz \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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 NNTP newsgroup(s).