Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Thierry BERTAUD <tbertaud@conforama.fr>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio-f1480f9: AIX 6.1 build KO against gcc function overlap
Date: Tue, 29 Dec 2015 08:34:50 -0700	[thread overview]
Message-ID: <5682A81A.8010008@kernel.dk> (raw)
In-Reply-To: <VI1PR05MB134330236BC82EF62F5219C0B1FC0@VI1PR05MB1343.eurprd05.prod.outlook.com>

On 12/28/2015 05:56 PM, Thierry BERTAUD wrote:
> Jens,
>
>> Fixed that new dependency, try pulling again :-)
> Yes fixed, i just have some warning.
> ----
> t/dedupe.c: In function 'dedupe_check':
> t/dedupe.c:97:2: warning: 'bytes' may be used uninitialized in this function [-Wmaybe-uninitialized]
>    return (ret & ~((uint64_t)blocksize - 1));
>    ^
> t/dedupe.c:87:22: note: 'bytes' was declared here
>     unsigned long long bytes;
>                        ^

That's the aix compiler being a bit too dumb to realize that 'bytes' is 
only used for a zero return of that function. You can safely ignore 
that, I can add a small patch to get rid of it.

>      CC t/debug.o
> ----
>
> What's the advantage to use 'lex/yacc for arithmetic'?

That you can have arithmetical expressions in your job files, that's all 
it provides.

> I disabled it in configure because i can't build and haved the following:
> ---
>     LEX lex.yy.c
> 0: Warning: 1285-300 The o flag is not valid.
> 0: Error: 1285-331 Cannot read input file lex.yy.c
> Makefile:300: recipe for target 'lex.yy.c' failed
> gmake: *** [lex.yy.c] Error 1

Hmm, I'll see if I can add a check in configure for whether or not lex 
requires -o to specify an output file. For now, just use --disable-lex.

-- 
Jens Axboe



  reply	other threads:[~2015-12-29 15:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-28 21:45 fio-f1480f9: AIX 6.1 build KO against gcc function overlap Thierry BERTAUD
2015-12-28 22:24 ` Andrey Kuzmin
2015-12-28 23:18   ` Thierry BERTAUD
2015-12-28 23:21 ` Jens Axboe
2015-12-28 23:34   ` Thierry BERTAUD
2015-12-28 23:46     ` Jens Axboe
2015-12-29  0:01       ` Thierry BERTAUD
2015-12-29  0:15         ` Jens Axboe
2015-12-29  0:30           ` Thierry BERTAUD
2015-12-29  0:39             ` Jens Axboe
2015-12-29  0:56               ` Thierry BERTAUD
2015-12-29 15:34                 ` Jens Axboe [this message]
2015-12-29 16:16                   ` Thierry BERTAUD
2015-12-29 21:10                     ` Thierry BERTAUD
2015-12-30  3:26                       ` Jens Axboe
2015-12-30  3:59                         ` Jens Axboe
2015-12-30  8:36                           ` Thierry BERTAUD
2015-12-30 16:38                             ` Jens Axboe
2015-12-30 16:50                               ` Jens Axboe
2015-12-30 16:51                                 ` Jens Axboe
2015-12-30 17:59                                   ` Thierry BERTAUD

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=5682A81A.8010008@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=tbertaud@conforama.fr \
    /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