Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alireza Haghdoost <haghdoost@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: competime_assert failure without -O3 optimization flag expected ?
Date: Mon, 29 Jun 2015 09:55:18 -0600	[thread overview]
Message-ID: <55916A66.5080303@kernel.dk> (raw)
In-Reply-To: <CAB-428=EKjcxK6J9OvKU1nM34Q998fN=LFQKgNgofeMb_cuY1g@mail.gmail.com>

On 06/29/2015 09:53 AM, Alireza Haghdoost wrote:
> Sure, I will investigate it. Just want to confirm the issue is in the
> compiletime_assert() code as you mentioned and it is not in that line
> of code that I cite in my last email. I managed to remedy this issue a
> little bit by using -O1 instead of -O3 but still the optimized program
> order is not exactly similar to the default source code order.

It bothers me too, I'll turn off optimizations for debugging things too, 
and just end up uncommenting the lines to make that work. Apparently it 
hasn't bothered me enough to fix it up yet, but I would love to see it 
fixed.

-- 
Jens Axboe



  reply	other threads:[~2015-06-29 15:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 14:46 competime_assert failure without -O3 optimization flag expected ? Alireza Haghdoost
2015-06-29 15:47 ` Jens Axboe
2015-06-29 15:53   ` Alireza Haghdoost
2015-06-29 15:55     ` Jens Axboe [this message]
2015-06-29 16:04       ` Jens Axboe
2015-06-29 17:42         ` Alireza Haghdoost
2015-06-29 17:50           ` Jens Axboe
2015-06-29 18:25             ` Alireza Haghdoost
2015-06-29 18:29               ` Jens Axboe
2015-06-29 18:58                 ` Alireza Haghdoost
2015-06-29 19:11                   ` Jens Axboe

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=55916A66.5080303@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=haghdoost@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