On Thu, Sep 24, 2020 at 9:48 AM H.J. Lu wrote:
>
> On Wed, Sep 16, 2020 at 4:47 AM Jakub Jelinek wrote:
> >
> > On Wed, Sep 16, 2020 at 12:34:50PM +0100, Richard Sandiford wrote:
> > > Jakub Jelinek via Gcc-patches writes:
> > > > On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches
On Wed, Sep 16, 2020 at 4:47 AM Jakub Jelinek wrote:
>
> On Wed, Sep 16, 2020 at 12:34:50PM +0100, Richard Sandiford wrote:
> > Jakub Jelinek via Gcc-patches writes:
> > > On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote:
> > >> Something like this for GCC 8 and 9.
> > >
>
On Wed, Sep 16, 2020 at 12:34:50PM +0100, Richard Sandiford wrote:
> Jakub Jelinek via Gcc-patches writes:
> > On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote:
> >> Something like this for GCC 8 and 9.
> >
> > Guess my preference would be to do this everywhere and then let'
Jakub Jelinek via Gcc-patches writes:
> On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote:
>> Something like this for GCC 8 and 9.
>
> Guess my preference would be to do this everywhere and then let's discuss if
> we change the warning into error there or keep it being deprec
On Mon, Sep 14, 2020 at 10:05 AM Jakub Jelinek wrote:
>
> On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote:
> > Something like this for GCC 8 and 9.
>
> Guess my preference would be to do this everywhere and then let's discuss if
The same patch also works on master branch.
On Mon, Sep 14, 2020 at 08:57:18AM -0700, H.J. Lu via Gcc-patches wrote:
> Something like this for GCC 8 and 9.
Guess my preference would be to do this everywhere and then let's discuss if
we change the warning into error there or keep it being deprecated.
Though, let's see what others want to sa
On Mon, Sep 14, 2020 at 8:12 AM H.J. Lu wrote:
>
> On Mon, Sep 14, 2020 at 7:35 AM Jakub Jelinek wrote:
> >
> > On Sat, Sep 12, 2020 at 10:11:36AM -0700, H.J. Lu via Gcc-patches wrote:
> > > Clobbering the stack pointer in asm statment has been deprecated. Adding
> > > the stack pointer register
On Mon, Sep 14, 2020 at 7:35 AM Jakub Jelinek wrote:
>
> On Sat, Sep 12, 2020 at 10:11:36AM -0700, H.J. Lu via Gcc-patches wrote:
> > Clobbering the stack pointer in asm statment has been deprecated. Adding
> > the stack pointer register to the clobber list has traditionally had some
> > undocume
On Sat, Sep 12, 2020 at 10:11:36AM -0700, H.J. Lu via Gcc-patches wrote:
> Clobbering the stack pointer in asm statment has been deprecated. Adding
> the stack pointer register to the clobber list has traditionally had some
> undocumented and somewhat obscure side-effects, including ICE. Issue
>
* Jakub Jelinek:
> On Sat, Sep 12, 2020 at 07:37:36PM +0200, Florian Weimer wrote:
>> * H. J. Lu via Gcc-patches:
>>
>> > +inform (input_location, "the value of the stack pointer after"
>> > +" an % statement must be the same as it was"
>> > +" before the statement");
On Sat, Sep 12, 2020 at 07:37:36PM +0200, Florian Weimer wrote:
> * H. J. Lu via Gcc-patches:
>
> > + inform (input_location, "the value of the stack pointer after"
> > + " an % statement must be the same as it was"
> > + " before the statement");
>
> Would it make sen
On Sat, Sep 12, 2020 at 10:37 AM Florian Weimer wrote:
>
> * H. J. Lu via Gcc-patches:
>
> > + inform (input_location, "the value of the stack pointer after"
> > + " an % statement must be the same as it was"
> > + " before the statement");
>
> Would it make sense
* H. J. Lu via Gcc-patches:
> + inform (input_location, "the value of the stack pointer after"
> + " an % statement must be the same as it was"
> + " before the statement");
Would it make sense to generate a stronger worded warning when
generating asynchronous un
Clobbering the stack pointer in asm statment has been deprecated. Adding
the stack pointer register to the clobber list has traditionally had some
undocumented and somewhat obscure side-effects, including ICE. Issue
a warning and ignore the clobbered stack pointer in asm statment.
gcc/
14 matches
Mail list logo
