bootstrap failure in stage3 (integer overflow in preprocessor expression)

Bug #500524 reported by Matthias Klose
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro GCC
Fix Released
Low
Ulrich Weigand
Linaro GCC Tracking
Fix Released
Undecided
Unassigned
gcc
Fix Released
Medium
gcc-4.4 (Ubuntu)
Fix Released
Undecided
Unassigned
gcc-snapshot (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: gcc-snapshot

see the upstream report

Related branches

Changed in gcc:
status: Unknown → New
Changed in gcc:
status: New → Confirmed
Changed in gcc:
status: Confirmed → In Progress
Changed in gcc:
status: In Progress → Confirmed
Changed in gcc:
status: Confirmed → Fix Released
Changed in gcc:
status: Fix Released → Confirmed
Revision history for this message
Matthias Klose (doko) wrote :

the bootstrap now works; the upstream report was opened again for gcc-4.4:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42509#c28

Changed in gcc-snapshot (Ubuntu):
importance: Undecided → High
status: New → Triaged
Matthias Klose (doko)
Changed in gcc-snapshot (Ubuntu):
status: Triaged → Fix Released
Matthias Klose (doko)
tags: added: toolchain
Changed in gcc-linaro:
assignee: nobody → Ulrich Weigand (uweigand)
Revision history for this message
Ulrich Weigand (uweigand) wrote :

I've looked into the history of the underlying problem a bit more and found out:
- in 4.3 and earlier, the problem didn't yet exist
- in 4.5 and later, the problem is fixed
- however, in 4.4, the problem exists as latent wrong-code generation bug

I've suggested on the gcc-patches list that it would be a good idea to backport the fix to 4.4. If they agree, we'd get the fix automatically when moving forward to 4.4.5. Otherwise, we have to decide whether to take the backport into Linaro GCC.

Revision history for this message
Ulrich Weigand (uweigand) wrote :

Richard Günther agreed to a 4.4 backport. Working on this now.

Changed in gcc-linaro:
status: New → In Progress
Revision history for this message
Ulrich Weigand (uweigand) wrote :

I've committed the fix to the upstream 4.4 branch now. Fix will be in 4.4.5 release.

Changed in gcc:
status: Confirmed → Fix Released
Revision history for this message
Michael Hope (michaelh1) wrote :

I'm experimenting with how to track where a fix landed upstream. Please ignore the 'Affects Linaro GCC Tracking' entry above.

Changed in gcc-linaro-tracking:
milestone: none → 4.4.5
Michael Hope (michaelh1)
Changed in gcc-linaro:
milestone: none → 4.4-2010.09-0
Revision history for this message
Matthias Klose (doko) wrote :

fixed in gcc-4.4 4.4.4-8ubuntu1

Changed in gcc-4.4 (Ubuntu):
status: New → Fix Released
Michael Hope (michaelh1)
Changed in gcc-linaro:
importance: Undecided → Low
Revision history for this message
Ulrich Weigand (uweigand) wrote :

Merge request into Linaro GCC 4.4 now pending.

Michael Hope (michaelh1)
Changed in gcc-linaro:
milestone: 4.4-2010.09-0 → 4.4-2010.08-0
Changed in gcc-linaro:
status: In Progress → Fix Committed
Michael Hope (michaelh1)
Changed in gcc-linaro:
status: Fix Committed → Fix Released
Michael Hope (michaelh1)
Changed in gcc-linaro-tracking:
status: New → Fix Committed
Revision history for this message
Andrew Stubbs (ams-codesourcery) wrote :
Changed in gcc-linaro-tracking:
status: Fix Committed → Fix Released
Changed in gcc:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.