On Thu, Apr 1, 2021 at 10:47 PM H.J. Lu wrote:
>
> On Thu, Apr 1, 2021 at 1:28 PM Jan Hubicka wrote:
> >
> > > On Thu, Apr 1, 2021 at 6:54 PM H.J. Lu wrote:
> > > >
> > > > Since uiret should be used only for user interrupt handler return, don't
> > > > generate uiret in interrupt handler return
On Thu, Apr 1, 2021 at 1:28 PM Jan Hubicka wrote:
>
> > On Thu, Apr 1, 2021 at 6:54 PM H.J. Lu wrote:
> > >
> > > Since uiret should be used only for user interrupt handler return, don't
> > > generate uiret in interrupt handler return with -mcmodel=kernel even if
> > > UINTR is enabled.
> >
> >
> On Thu, Apr 1, 2021 at 6:54 PM H.J. Lu wrote:
> >
> > Since uiret should be used only for user interrupt handler return, don't
> > generate uiret in interrupt handler return with -mcmodel=kernel even if
> > UINTR is enabled.
>
> NAK, -mcmodel should not affect ISAs, in the same way it doesn't s
On Thu, Apr 1, 2021 at 6:54 PM H.J. Lu wrote:
>
> Since uiret should be used only for user interrupt handler return, don't
> generate uiret in interrupt handler return with -mcmodel=kernel even if
> UINTR is enabled.
NAK, -mcmodel should not affect ISAs, in the same way it doesn't switch off SSE.
On 1 April 2021 20:31:13 CEST, Bernhard Reutner-Fischer
wrote:
>On 1 April 2021 18:54:07 CEST, "H.J. Lu via Gcc-patches"
> wrote:
>>Since uiret should be used only for user interrupt handler return,
>>don't
>>generate uiret in interrupt handler return with -mcmodel=kernel even
>if
>>UINTR is enab
On 1 April 2021 18:54:07 CEST, "H.J. Lu via Gcc-patches"
wrote:
>Since uiret should be used only for user interrupt handler return,
>don't
>generate uiret in interrupt handler return with -mcmodel=kernel even if
>UINTR is enabled.
>
>gcc/
>
> PR target/99870
> * config/i386/i386.md (i
Since uiret should be used only for user interrupt handler return, don't
generate uiret in interrupt handler return with -mcmodel=kernel even if
UINTR is enabled.
gcc/
PR target/99870
* config/i386/i386.md (interrupt_return): Don't generate uiret
for -mcmodel=kernel.
gcc/
