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 13:11:36 -0600 [thread overview]
Message-ID: <55919868.4010504@kernel.dk> (raw)
In-Reply-To: <CAB-428kYoWm-SqfCpQRa2z6-fb=7X+kkNC7hfOV8HOUU-TV4PQ@mail.gmail.com>
On 06/29/2015 12:58 PM, Alireza Haghdoost wrote:
> Make sens Jens. I did not get what you told me in the first place. Let
> me know if this would fix it. It works for me with GCC 4.6 (patch file
> is also attached):
This is perfect! Thanks, committed:
http://git.kernel.dk/cgit/fio/commit/?id=5018f79f6d8da82b6fafbbeeebdecb3799788bc3
--
Jens Axboe
prev parent reply other threads:[~2015-06-29 19:11 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
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 [this message]
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=55919868.4010504@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