This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/80947] [6/7/8 Regression] Different visibility for the lambda and its capture list members with -fvisibility=hidden
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 15 Sep 2017 12:52:05 +0000
- Subject: [Bug c++/80947] [6/7/8 Regression] Different visibility for the lambda and its capture list members with -fvisibility=hidden
- Auto-submitted: auto-generated
- References: <bug-80947-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80947
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Vlad Zolotarov from comment #10)
> (In reply to Jonathan Wakely from comment #9)
> > It says not to attach an archive containing the things we don't want (e.g.
> > sources without includes). And a .gz file is not an archive.
>
>
> "Please avoid posting an archive (.tar, .shar or .zip); we generally need
And those are all archive formats, not just compression formats like gzip.
> just a single file to reproduce the bug (the .i/.ii/.f preprocessed file),
A gzipped single file is a single file.
> and, by storing it in an archive, you're just making our volunteers' jobs
> harder."
A gzipped file is not an archive.
An attachment that is a URL that must be copied and pasted to get a Google Docs
page with data that must be copied and pasted or downloaded is also making it
harder!
> But if you insist I can gzip and post it. Whatever makes it easier to fix
> the issue. Please, let me know if that's what you want.
There's no need now because comment 4 shows the issue, but next time yes,
please attach the preprocessed source directly. If it's too big compress it, or
better still reduce it: https://gcc.gnu.org/wiki/A_guide_to_testcase_reduction
That way the reproducer is in our bugzilla permanently. Files hosted externally
might go away or change, so we want the file *here*.