public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Porting to gcc 11 / intrinsics
Date: Tue, 24 Aug 2021 22:45:58 -0400	[thread overview]
Message-ID: <CAF1jjLuE_YSw-iqKEQi7EdPRaFkMqk6-=V21Fg9rzjCKb3m7zQ@mail.gmail.com> (raw)
In-Reply-To: <CA+=Sn1nQd8=WhWPgrhV=+tD1Nf_fGgU4=wL5n5sn9sUGhpRGaA@mail.gmail.com>

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.

      reply	other threads:[~2021-08-25  2:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 17:16 NightStrike
2021-08-25  1:38 ` NightStrike
2021-08-25  2:21   ` Andrew Pinski
2021-08-25  2:45     ` NightStrike [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='CAF1jjLuE_YSw-iqKEQi7EdPRaFkMqk6-=V21Fg9rzjCKb3m7zQ@mail.gmail.com' \
    --to=nightstrike@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pinskia@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 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).