All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
	joel@jms.id.au, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 5/5] powerpc: Remove -mno-sched-epilog
Date: Fri, 14 Sep 2018 20:04:11 -0500	[thread overview]
Message-ID: <20180915010410.GA23155@gate.crashing.org> (raw)
In-Reply-To: <CAKwvOdmsSbrw7oLZHWTseqxLocPmuXV=cnxSi2zskAmd9zKo0Q@mail.gmail.com>

On Fri, Sep 14, 2018 at 03:20:18PM -0700, Nick Desaulniers wrote:
> On Fri, Sep 14, 2018 at 2:56 PM Segher Boessenkool
> <segher@kernel.crashing.org> wrote:
> > On Sat, Sep 15, 2018 at 06:43:05AM +1000, Nicholas Piggin wrote:
> > > On Fri, 14 Sep 2018 11:03:38 -0700
> > > Nick Desaulniers <ndesaulniers@google.com> wrote:
> > >
> > > Sorry I forgot to cc you. This has links to some of the sched
> > > epilog bugs.
> > >
> > > https://marc.info/?l=linuxppc-embedded&m=153690223909654&w=2
> 
> Cool, cc me on the thread if you'd like me to add my reviewed-by tag
> visibly on the thread.
> 
> > PR44199 was backported to 4.4 and PR52828 is fixed in 4.8.
> 
> Are those GCC versions? If so, what does that mean for the users of
> the many GCC releases between 4.4 and 4.8?

Yes, GCC bug 44199 was fixed in GCC version 4.4, etc.  It of course also
is fixed in all later versions; so GCC releases between 4.4 and 4.8 have
the fix for PR44199 but not that for PR52828.

I didn't check exactly what 4.4.x versions have the fix, etc.  I always
assume anyone using x.y.z uses the highest z available.

I don't know if those are the only fixes you need; those are the two
bugs mentioned in Nicholas' patch (that MARC link above).


Segher

      reply	other threads:[~2018-09-15  1:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14  4:06 [PATCH v2 0/5] powerpc: Clang build fixes Joel Stanley
2018-09-14  4:06 ` [PATCH v2 1/5] powerpc/Makefiles: Fix clang/llvm build Joel Stanley
2018-09-14 17:41   ` Nick Desaulniers
2018-09-20  7:04     ` Joel Stanley
2018-09-14  4:06 ` [PATCH v2 2/5] powerpc/boot: Fix crt0.S syntax for clang Joel Stanley
2018-09-14 17:47   ` Nick Desaulniers
2018-09-14 21:08     ` Segher Boessenkool
2018-09-17 20:41       ` Nick Desaulniers
2018-09-18  1:08         ` Joel Stanley
2018-09-18 10:53           ` Michael Ellerman
2018-09-14  4:06 ` [PATCH v2 3/5] powerpc/boot: Ensure _zimage_start is a weak symbol Joel Stanley
2018-09-14 17:50   ` Nick Desaulniers
2018-09-20  4:21   ` [v2,3/5] " Michael Ellerman
2018-09-14  4:06 ` [PATCH v2 4/5] powerpc: Fix duplicate const clang warning in user access code Joel Stanley
2018-09-14 17:57   ` Nick Desaulniers
2018-09-19  7:45     ` Joel Stanley
2018-09-20  4:54       ` Christophe LEROY
2018-09-20 12:35         ` Michael Ellerman
2018-09-20  4:21   ` [v2, " Michael Ellerman
2018-09-14  4:06 ` [PATCH v2 5/5] powerpc: Remove -mno-sched-epilog Joel Stanley
2018-09-14  5:06   ` Nicholas Piggin
2018-09-14 18:03     ` Nick Desaulniers
2018-09-14 20:43       ` Nicholas Piggin
2018-09-14 21:18         ` Segher Boessenkool
2018-09-14 22:20           ` Nick Desaulniers
2018-09-15  1:04             ` Segher Boessenkool [this message]

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=20180915010410.GA23155@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=joel@jms.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ndesaulniers@google.com \
    --cc=npiggin@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.