https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
--- Comment #7 from Arseny Solokha ---
(In reply to Martin Liška from comment #5)
> Yes, but I was thinking that you are using a nighly builds from trunk?
I use weekly snapshots. Sorry for not mentioning it earlier.
> Even my distribution relea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
Martin Liška changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
--- Comment #5 from Martin Liška ---
(In reply to Arseny Solokha from comment #4)
> (In reply to Martin Liška from comment #3)
> > For next PRs,
> > please output content of gcc -v so that we can identify a single commit.
>
> Sure, but how can t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
--- Comment #4 from Arseny Solokha ---
(In reply to Martin Liška from comment #3)
> For next PRs,
> please output content of gcc -v so that we can identify a single commit.
Sure, but how can this possibly help to identify a commit? I dont' have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
--- Comment #3 from Martin Liška ---
(In reply to Arseny Solokha from comment #2)
> I also cannot reproduce it anymore w/ gcc-8.0.0-alpha20170806 snapshot. It
> must be fixed or made latent some time in between.
>
> % powerpc-e300c3-linux-gnu-gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
--- Comment #2 from Arseny Solokha ---
I also cannot reproduce it anymore w/ gcc-8.0.0-alpha20170806 snapshot. It must
be fixed or made latent some time in between.
% powerpc-e300c3-linux-gnu-gcc-8.0.0-alpha20170806 -Q --help=target | grep -e
ma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81301
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
