public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lightningdzeyenr at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103701] C++20 modules create internal compiler error at import_export_decl
Date: Tue, 14 Dec 2021 03:45:25 +0000	[thread overview]
Message-ID: <bug-103701-4-pIOziK5wjd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103701-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Jackson Huff <lightningdzeyenr at gmail dot com> ---
Created attachment 51996
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51996&action=edit
The preprocessed file that causes the compiler error

The original file upload failed because the preprocessed source is double the
maximum size, so this new one should work

  reply	other threads:[~2021-12-14  3:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  3:41 [Bug c++/103701] New: " lightningdzeyenr at gmail dot com
2021-12-14  3:45 ` lightningdzeyenr at gmail dot com [this message]
2021-12-14  4:02 ` [Bug c++/103701] " pinskia at gcc dot gnu.org
2024-02-01 23:01 ` pinskia at gcc dot gnu.org
2024-02-01 23:19 ` 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-103701-4-pIOziK5wjd@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).