public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107748] [13 Regression] Isn't _mm_cvtsbh_ss incorrect?
Date: Mon, 21 Nov 2022 09:30:08 +0000	[thread overview]
Message-ID: <bug-107748-4-TIfDNcTrq2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107748-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:ec8ec09f9414be871e322fecf4ebf53e3687bd22

commit r13-4187-gec8ec09f9414be871e322fecf4ebf53e3687bd22
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Mon Nov 21 10:28:27 2022 +0100

    i386: Uglify some local identifiers in *intrin.h [PR107748]

    While reporting PR107748 (where is a problem with non-uglified names,
    but I've left it out because it needs fixing anyway), I've noticed
    various spots where identifiers in *intrin.h headers weren't uglified.
    The following patch fixed those that are related to unions (I've grepped
    for [a-zA-Z]\.[a-zA-Z] spots).
    The reason we need those to be uglified is the same as why the arguments
    of the inlines are __ prefixed and most of automatic vars in the inlines
    - say a, v or u aren't part of implementation namespace and so users could
     #define u whatever->something
     #include <x86intrin.h>
    and it should still work, as long as u is not e.g. one of the names
    of the functions/macros the header provides (_mm* etc.).

    2022-11-21  Jakub Jelinek  <jakub@redhat.com>

            PR target/107748
            * config/i386/avx512fp16intrin.h (_mm512_castph512_ph128,
            _mm512_castph512_ph256, _mm512_castph128_ph512,
            _mm512_castph256_ph512, _mm512_set1_pch): Uglify names of local
            variables and union members.
            * config/i386/avx512fp16vlintrin.h (_mm256_castph256_ph128,
            _mm256_castph128_ph256, _mm256_set1_pch, _mm_set1_pch): Likewise.
            * config/i386/smmintrin.h (_mm_extract_ps): Likewise.

  parent reply	other threads:[~2022-11-21  9:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 10:10 [Bug target/107748] New: " jakub at gcc dot gnu.org
2022-11-18 10:11 ` [Bug target/107748] " jakub at gcc dot gnu.org
2022-11-18 10:14 ` jakub at gcc dot gnu.org
2022-11-18 11:31 ` crazylht at gmail dot com
2022-11-18 11:46 ` jakub at gcc dot gnu.org
2022-11-18 12:04 ` jakub at gcc dot gnu.org
2022-11-21  9:30 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-21  9:33 ` cvs-commit at gcc dot gnu.org
2022-11-21  9:35 ` cvs-commit at gcc dot gnu.org
2022-11-21  9:36 ` jakub at gcc dot gnu.org
2022-11-22  5:16 ` crazylht at gmail dot com
2022-11-28  1:03 ` cvs-commit at gcc dot gnu.org
2022-11-28  1:03 ` crazylht at gmail dot com
2022-11-29 14:41 ` jakub at gcc dot gnu.org
2023-05-03 15:19 ` cvs-commit at gcc dot gnu.org

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=bug-107748-4-TIfDNcTrq2@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).