public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Porting to gcc 11 / intrinsics
@ 2021-08-09 17:16 NightStrike
  2021-08-25  1:38 ` NightStrike
  0 siblings, 1 reply; 4+ messages in thread
From: NightStrike @ 2021-08-09 17:16 UTC (permalink / raw)
  To: gcc

When porting to GCC 11, care must be taken to adjust includes of GCC
intrinsic headers due to this change:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97148

That should be reflected in:

https://gcc.gnu.org/gcc-11/porting_to.html

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Porting to gcc 11 / intrinsics
  2021-08-09 17:16 Porting to gcc 11 / intrinsics NightStrike
@ 2021-08-25  1:38 ` NightStrike
  2021-08-25  2:21   ` Andrew Pinski
  0 siblings, 1 reply; 4+ messages in thread
From: NightStrike @ 2021-08-25  1:38 UTC (permalink / raw)
  To: gcc

Should I make this a bugzilla? I guess I figured that wouldn't be
appropriate.

On Mon, Aug 9, 2021, 07:16 NightStrike <nightstrike@gmail.com> wrote:

> When porting to GCC 11, care must be taken to adjust includes of GCC
> intrinsic headers due to this change:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97148
>
> That should be reflected in:
>
> https://gcc.gnu.org/gcc-11/porting_to.html
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Porting to gcc 11 / intrinsics
  2021-08-25  1:38 ` NightStrike
@ 2021-08-25  2:21   ` Andrew Pinski
  2021-08-25  2:45     ` NightStrike
  0 siblings, 1 reply; 4+ messages in thread
From: Andrew Pinski @ 2021-08-25  2:21 UTC (permalink / raw)
  To: NightStrike; +Cc: gcc

On Tue, Aug 24, 2021 at 6:39 PM NightStrike via Gcc <gcc@gcc.gnu.org> wrote:
>
> Should I make this a bugzilla? I guess I figured that wouldn't be
> appropriate.

I don't see a reason why this should go into porting as there was no
change needed from previous versions of GCC.
Supporting -mno-sse is a new feature even.

Thanks,
Andrew


>
> On Mon, Aug 9, 2021, 07:16 NightStrike <nightstrike@gmail.com> wrote:
>
> > When porting to GCC 11, care must be taken to adjust includes of GCC
> > intrinsic headers due to this change:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97148
> >
> > That should be reflected in:
> >
> > https://gcc.gnu.org/gcc-11/porting_to.html
> >

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Porting to gcc 11 / intrinsics
  2021-08-25  2:21   ` Andrew Pinski
@ 2021-08-25  2:45     ` NightStrike
  0 siblings, 0 replies; 4+ messages in thread
From: NightStrike @ 2021-08-25  2:45 UTC (permalink / raw)
  To: Andrew Pinski; +Cc: gcc

On Tue, Aug 24, 2021 at 10:21 PM Andrew Pinski <pinskia@gmail.com> wrote:
>
> On Tue, Aug 24, 2021 at 6:39 PM NightStrike via Gcc <gcc@gcc.gnu.org> wrote:
> > On Mon, Aug 9, 2021, 07:16 NightStrike <nightstrike@gmail.com> wrote:
> >
> > > When porting to GCC 11, care must be taken to adjust includes of GCC
> > > intrinsic headers due to this change:
> > >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97148
> > >
> > > That should be reflected in:
> > >
> > > https://gcc.gnu.org/gcc-11/porting_to.html
> > Should I make this a bugzilla? I guess I figured that wouldn't be
> > appropriate.
>
> I don't see a reason why this should go into porting as there was no
> change needed from previous versions of GCC.
> Supporting -mno-sse is a new feature even.

(Fixed my top posting gaff, sorry about that)

Ok.  I would have found the information useful, perhaps another place
would be better?  In general, documentation here is lacking.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2021-08-25  2:46 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-09 17:16 Porting to gcc 11 / intrinsics NightStrike
2021-08-25  1:38 ` NightStrike
2021-08-25  2:21   ` Andrew Pinski
2021-08-25  2:45     ` NightStrike

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).