https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69175
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-01-07
CC| |jakub at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I actually see a hang in schedule_block,
with -fdump-rtl-sched2-details -fsched-verbose=2 I'm seeing
...
;; Ready list (t = 8):
;; Advancing clock by 128 cycle[s] to 137
;; Ready list after queue_to_ready:
;; Advancing clock by 128 cycle[s] to 266
;; Ready list after queue_to_ready:
;; Advancing clock by 128 cycle[s] to 395
;; Ready list after queue_to_ready:
...
;; Advancing clock by 128 cycle[s] to 41674361
;; Ready list after queue_to_ready:
;; Advancing clock by 128 cycle[s] to 41674490
;; Ready list after queue_to_ready:
;; Advancing clock by 128 cycle[s] to 41674619
but perhaps my cross is misconfigured or I've just not waited long enough,
maybe if the clock counters wrap something weird happens.
