public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/95684] New: internal compiler error: Segmentation fault
@ 2020-06-15 15:18 janezz55 at gmail dot com
  2020-06-15 15:19 ` [Bug c++/95684] " janezz55 at gmail dot com
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: janezz55 at gmail dot com @ 2020-06-15 15:18 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 95684
           Summary: internal compiler error: Segmentation fault
           Product: gcc
           Version: 10.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: janezz55 at gmail dot com
  Target Milestone: ---

source code is at: https://github.com/user1095108/generic

I do this:

g++ -std=c++17 forwarder.cpp -o f

I get this:

In file included from forwarder.cpp:3:
forwarder.hpp: In instantiation of 'class
gnr::detail::forwarder::forwarder_impl2<void(const S&), 32, true>':
forwarder.hpp:82:7:   required from 'class
gnr::detail::forwarder::forwarder_impl<void(const S&) noexcept, 32>'
forwarder.hpp:90:7:   required from 'class gnr::forwarder<void(const S&)
noexcept>'
forwarder.cpp:17:44:   required from here
forwarder.hpp:29:7: internal compiler error: Segmentation fault
   29 |   R (*stub_)(void*, A&&...) noexcept(E) {};
      |       ^~~~~
Please submit a full bug report,

gcc version 10.1.0 (GCC)

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c++/95684] internal compiler error: Segmentation fault
  2020-06-15 15:18 [Bug c++/95684] New: internal compiler error: Segmentation fault janezz55 at gmail dot com
@ 2020-06-15 15:19 ` janezz55 at gmail dot com
  2020-06-15 15:22 ` mpolacek at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: janezz55 at gmail dot com @ 2020-06-15 15:19 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Janez Zemva <janezz55 at gmail dot com> ---
Everything works with clang version 10.0.0.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c++/95684] internal compiler error: Segmentation fault
  2020-06-15 15:18 [Bug c++/95684] New: internal compiler error: Segmentation fault janezz55 at gmail dot com
  2020-06-15 15:19 ` [Bug c++/95684] " janezz55 at gmail dot com
@ 2020-06-15 15:22 ` mpolacek at gcc dot gnu.org
  2020-06-15 16:09 ` janezz55 at gmail dot com
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2020-06-15 15:22 UTC (permalink / raw)
  To: gcc-bugs

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mpolacek at gcc dot gnu.org

--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Janez Zemva from comment #0)
> source code is at: https://github.com/user1095108/generic
> 
> I do this:
> 
> g++ -std=c++17 forwarder.cpp -o f
> 
> I get this:
> 
> In file included from forwarder.cpp:3:
> forwarder.hpp: In instantiation of 'class
> gnr::detail::forwarder::forwarder_impl2<void(const S&), 32, true>':
> forwarder.hpp:82:7:   required from 'class
> gnr::detail::forwarder::forwarder_impl<void(const S&) noexcept, 32>'
> forwarder.hpp:90:7:   required from 'class gnr::forwarder<void(const S&)
> noexcept>'
> forwarder.cpp:17:44:   required from here
> forwarder.hpp:29:7: internal compiler error: Segmentation fault
>    29 |   R (*stub_)(void*, A&&...) noexcept(E) {};
>       |       ^~~~~
> Please submit a full bug report,

...with preprocessed source if appropriate.

Can you provide that?

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c++/95684] internal compiler error: Segmentation fault
  2020-06-15 15:18 [Bug c++/95684] New: internal compiler error: Segmentation fault janezz55 at gmail dot com
  2020-06-15 15:19 ` [Bug c++/95684] " janezz55 at gmail dot com
  2020-06-15 15:22 ` mpolacek at gcc dot gnu.org
@ 2020-06-15 16:09 ` janezz55 at gmail dot com
  2020-06-15 16:19 ` mpolacek at gcc dot gnu.org
  2020-06-15 16:33 ` msebor at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: janezz55 at gmail dot com @ 2020-06-15 16:09 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #3 from Janez Zemva <janezz55 at gmail dot com> ---
Isn't a link to the source code sufficient? You can generate your own, if you
want.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c++/95684] internal compiler error: Segmentation fault
  2020-06-15 15:18 [Bug c++/95684] New: internal compiler error: Segmentation fault janezz55 at gmail dot com
                   ` (2 preceding siblings ...)
  2020-06-15 16:09 ` janezz55 at gmail dot com
@ 2020-06-15 16:19 ` mpolacek at gcc dot gnu.org
  2020-06-15 16:33 ` msebor at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: mpolacek at gcc dot gnu.org @ 2020-06-15 16:19 UTC (permalink / raw)
  To: gcc-bugs

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

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Never mind.  I've actually already fixed this one.

*** This bug has been marked as a duplicate of bug 95562 ***

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug c++/95684] internal compiler error: Segmentation fault
  2020-06-15 15:18 [Bug c++/95684] New: internal compiler error: Segmentation fault janezz55 at gmail dot com
                   ` (3 preceding siblings ...)
  2020-06-15 16:19 ` mpolacek at gcc dot gnu.org
@ 2020-06-15 16:33 ` msebor at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: msebor at gcc dot gnu.org @ 2020-06-15 16:33 UTC (permalink / raw)
  To: gcc-bugs

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |msebor at gcc dot gnu.org

--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Janez Zemva from comment #3)
> Isn't a link to the source code sufficient? You can generate your own, if
> you want.

No, links to other sites for us to download code from aren't sufficient.  What
we ask for is documented in https://gcc.gnu.org/bugs/#need, namely:

Please include all of the following items, the first three of which can be
obtained from the output of gcc -v:
    ...
    the preprocessed file (*.i*) that triggers the bug, generated by adding
-save-temps to the complete compilation command, or, in the case of a bug
report for the GNAT front end, a complete set of source files (see below).

One reason for this is so that when the site becomes unavailable or the
information on it changes the bug report can still be properly analyzed.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-06-15 16:33 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-15 15:18 [Bug c++/95684] New: internal compiler error: Segmentation fault janezz55 at gmail dot com
2020-06-15 15:19 ` [Bug c++/95684] " janezz55 at gmail dot com
2020-06-15 15:22 ` mpolacek at gcc dot gnu.org
2020-06-15 16:09 ` janezz55 at gmail dot com
2020-06-15 16:19 ` mpolacek at gcc dot gnu.org
2020-06-15 16:33 ` msebor at gcc dot gnu.org

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).