Re: MIT discovered issue with gcc

To: debian-user@lists.debian.org
Subject: Re: MIT discovered issue with gcc
From: Neal Murphy <neal.p.murphy@alum.wpi.edu>
Date: Sat, 23 Nov 2013 16:36:18 -0500
Message-id: <[🔎] 201311231636.18718.neal.p.murphy@alum.wpi.edu>
Reply-to: neal.p.murphy@alum.wpi.edu
In-reply-to: <[🔎] 52911CB9.5010002@hardwarefreak.com>
References: <[🔎] 52900522.9040507@affinityvision.com.au> <[🔎] 52900637.1080600@affinityvision.com.au> <[🔎] 52911CB9.5010002@hardwarefreak.com>

On Saturday, November 23, 2013 04:23:05 PM Stan Hoeppner wrote:

> I didn't read the full paper yet, but I'm wondering how/if the
> optimization flag plays a part in this.  I.e. does "O2" produce these
> bugs but "OO" (default) or "Og" (debugging) does not?

Or -O3...

Reply to:

References:
- MIT discovered issue with gcc
  - From: Andrew McGlashan <andrew.mcglashan@affinityvision.com.au>
- Re: MIT discovered issue with gcc
  - From: Andrew McGlashan <andrew.mcglashan@affinityvision.com.au>
- Re: MIT discovered issue with gcc
  - From: Stan Hoeppner <stan@hardwarefreak.com>

Prev by Date: Re: MIT discovered issue with gcc
Next by Date: Re: MIT discovered issue with gcc
Previous by thread: Re: MIT discovered issue with gcc
Next by thread: Re: MIT discovered issue with gcc
Index(es):
- Date
- Thread