[Bug tree-optimization/82073] internal compiler error: in pop_to_marker, at tree-ssa-scopedtables.c

2017-09-05 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82073

Eric Gallager  changed:

   What|Removed |Added

 CC||egallager at gcc dot gnu.org

--- Comment #1 from Eric Gallager  ---
Could you post the output of g++ -v so we have version and target info please?

[Bug tree-optimization/82073] internal compiler error: in pop_to_marker, at tree-ssa-scopedtables.c

2017-09-05 Thread vsevolod.livinskij at frtk dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82073

--- Comment #2 from Vsevolod Livinskiy  ---
(In reply to Eric Gallager from comment #1)
> Could you post the output of g++ -v so we have version and target info
> please?
Revision is 251589

>$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/gcc/x86_64-pc-linux-gnu/8.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /gcc-dev/bin-trunk --disable-bootstrap
Thread model: posix
gcc version 8.0.0 20170901 (experimental) (GCC)

[Bug tree-optimization/82073] internal compiler error: in pop_to_marker, at tree-ssa-scopedtables.c

2018-10-10 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82073

Eric Gallager  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #3 from Eric Gallager  ---
(In reply to Vsevolod Livinskiy from comment #2)
> (In reply to Eric Gallager from comment #1)
> > Could you post the output of g++ -v so we have version and target info
> > please?
> Revision is 251589
> 
> >$ g++ -v
> Using built-in specs.
> COLLECT_GCC=g++
> COLLECT_LTO_WRAPPER=/gcc/x86_64-pc-linux-gnu/8.0.0/lto-wrapper
> Target: x86_64-pc-linux-gnu
> Configured with: /gcc-dev/bin-trunk --disable-bootstrap
> Thread model: posix
> gcc version 8.0.0 20170901 (experimental) (GCC)

I can't reproduce with either 8.2 or trunk revision 264045 on
x86_64-apple-darwin10. Feel free to reopen if it still happens for you,
although if it does, it's probably a GNU/Linux-specific issue, so the component
would then be "target" instead.