https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
--- Comment #6 from vehre at gcc dot gnu.org ---
I am waiting for one week to pass without complaints before closing the pr as
resolved fixed to prevent resolved -> reopened cycles. Will mark as resolved ->
fixed on Feb. 3,. Sorry for not communic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
--- Comment #5 from janus at gcc dot gnu.org ---
Anything left to do here? Is there a particular reason the status is "WAITING"?
What are we waiting for?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
--- Comment #4 from vehre at gcc dot gnu.org ---
Author: vehre
Date: Wed Jan 27 14:48:04 2016
New Revision: 232876
URL: https://gcc.gnu.org/viewcvs?rev=232876&root=gcc&view=rev
Log:
gcc/testsuite/ChangeLog:
2016-01-27 Andre Vehreschild
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
Andrew Pinski changed:
What|Removed |Added
Keywords||wrong-code
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
--- Comment #3 from Rich Townsend ---
Proposed patch appears to work in the real-world case I'm focused on. Thanks!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|WAITING
--- Comment #2 from ve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|un
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69268
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
10 matches
Mail list logo