From: Steve Magnani <steve.magnani@digidescorp.com>
To: "Dorau, Lukasz" <lukasz.dorau@intel.com>,
Richard Weinberger <richard.weinberger@gmail.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Why is (2 < 2) true? Is it a gcc bug?
Date: Fri, 17 Jan 2014 09:47:05 -0600 [thread overview]
Message-ID: <52D95079.1060803@digidescorp.com> (raw)
In-Reply-To: <D9FFE20C522965449E182ACE73889AEB1A6A3592@IRSMSX105.ger.corp.intel.com>
On 01/17/2014 08:55 AM, Dorau, Lukasz wrote:
> On Friday, January 17, 2014 2:58 PM Richard Weinberger <richard.weinberger@gmail.com> wrote:
>> Can you reproduce this using a standalone test?
>> I.e:
>> #include <assert.h>
>>
>> int main()
>> {
>> assert(2 < 2 != 1);
>>
>> return 0;
>> }
>>
> No, I can't of course.
>
The test might need to be more complex in order to prevent the compiler from optimizing away the issue. Or, you could try -O0.
------------------------------------------------------------------------
Steven J. Magnani "I claim this network for MARS!
www.digidescorp.com Earthling, return my space modulator!"
#include <standard.disclaimer>
next prev parent reply other threads:[~2014-01-17 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 13:37 Why is (2 < 2) true? Is it a gcc bug? Dorau, Lukasz
2014-01-17 13:55 ` Dorau, Lukasz
2014-01-17 16:40 ` Sebastian Riemer
2014-01-17 17:00 ` Dorau, Lukasz
2014-01-17 13:58 ` Richard Weinberger
2014-01-17 14:55 ` Dorau, Lukasz
2014-01-17 15:47 ` Steve Magnani [this message]
2014-01-17 17:58 ` Alexei Starovoitov
2014-01-17 19:58 ` Alexei Starovoitov
2014-01-17 20:27 ` Andi Kleen
2014-01-17 21:02 ` Markus Trippelsdorf
2014-01-17 21:43 ` Alexei Starovoitov
2014-01-18 11:31 ` Dorau, Lukasz
2014-01-20 19:43 ` Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52D95079.1060803@digidescorp.com \
--to=steve.magnani@digidescorp.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lukasz.dorau@intel.com \
--cc=richard.weinberger@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox