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 preprocessor/101168] gnu++14 complains about altivec types defined with using keyword in the same file with preprocessor macros
Date: Tue, 10 May 2022 03:36:36 +0000	[thread overview]
Message-ID: <bug-101168-4-4FRQP2moSo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101168-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>:

https://gcc.gnu.org/g:067fe66c8ba9b16feacf66fce9ae668091e42821

commit r13-220-g067fe66c8ba9b16feacf66fce9ae668091e42821
Author: Jiufu Guo <guojiufu@linux.ibm.com>
Date:   Mon May 9 17:48:00 2022 +0800

    rs6000: avoid peeking eof after __vector

    There is a rare corner case: where vector is followed only by one
    valid identifer and the ";" which is near the end of the file.

    Like the case in PR101168:
    using vdbl =  __vector double;
    #define BREAK 1

    For this case, "vector double" is followed by CPP_SEMICOLON and then
    EOF.  There is no more tokens need to check for this case.

            PR preprocessor/101168

    gcc/ChangeLog:

            * config/rs6000/rs6000-c.cc (rs6000_macro_to_expand):
            Avoid empty identifier.

    gcc/testsuite/ChangeLog:

            * g++.target/powerpc/pr101168.C: New test.

  parent reply	other threads:[~2022-05-10  3:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 18:48 [Bug c++/101168] New: " tuliom at ascii dot art.br
2022-03-18  5:54 ` [Bug preprocessor/101168] " guojiufu at gcc dot gnu.org
2022-05-10  3:36 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-12  2:53 ` guojiufu at gcc dot gnu.org
2024-03-26  6:59 ` pinskia at gcc dot gnu.org
2024-03-26  7:01 ` pinskia 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-101168-4-4FRQP2moSo@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).