From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] fio: disable compiler optimizations
Date: Tue, 21 Aug 2018 15:25:09 +0800 [thread overview]
Message-ID: <5B7BBE55.3000107@windriver.com> (raw)
In-Reply-To: <CAMKF1so-+gSYZJGEJnaY9b_CT0fqDAWdAKMHtQxp+=OtJYESVA@mail.gmail.com>
On 2018年08月21日 15:24, Khem Raj wrote:
> On Tue, Aug 21, 2018 at 12:21 AM Yu, Mingli <mingli.yu@windriver.com> wrote:
>>
>>
>>
>> On 2018年08月21日 15:19, Khem Raj wrote:
>>> On Mon, Aug 20, 2018 at 2:42 AM <mingli.yu@windriver.com> wrote:
>>>>
>>>> From: Mingli Yu <Mingli.Yu@windriver.com>
>>>>
>>>> Add parameter "--disable-optimizations" to
>>>> configure script to disable compiler optimizations
>>>> to fix below issue:
>>>> $ gdb /usr/bin/fio
>>>> (gdb) r -h
>>>> Starting program: /usr/bin/fio -h
>>>> [Thread debugging using libthread_db enabled]
>>>> Using host libthread_db library "/lib64/libthread_db.so.1".
>>>>
>>>> Program received signal SIGILL, Illegal instruction.
>>>> 0x0000000000407220 in prio_tree_init () at lib/prio_tree.c:61
>>>> 61 index_bits_to_maxindex[i] = (1UL << (i + 1)) - 1;
>>>> (gdb) bt
>>>> #0 0x0000000000407220 in prio_tree_init () at lib/prio_tree.c:61
>>>> #1 0x0000000000482208 in __libc_csu_init (argc=argc@entry=2,
>>>> argv=argv@entry=0x7fffffffecc8, envp=0x7fffffffece0)
>>>> at /usr/src/debug/glibc/2.26-r0/git/csu/elf-init.c:88
>>>> #2 0x00000031c742095e in __libc_start_main (main=0x407700 <main>, argc=2,
>>>> argv=0x7fffffffecc8, init=0x4821b6 <__libc_csu_init>,
>>>> fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffecb8)
>>>> at /usr/src/debug/glibc/2.26-r0/git/csu/libc-start.c:264
>>>> #3 0x00000000004077ea in _start () at ../sysdeps/x86_64/start.S:120
>>>>
>>>
>>> Please check if you see this issue on master branch
>>> secondly, while you are here please upgrade to 3.8 release and see
>>> if this fixes the issue you are seeing.
>>
>> Yes, this issue exists in master, and even upgrade to 3.8, the issue
>> still exist.
>>
>
> OK. lets update regardless.
Okay, I will send v2 to include the upgrade patch.
Thanks,
>
>> Thanks,
>>
>>>
>>>> Signed-off-by: Mingli Yu <Mingli.Yu@windriver.com>
>>>> ---
>>>> meta-oe/recipes-benchmark/fio/fio_3.7.bb | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/meta-oe/recipes-benchmark/fio/fio_3.7.bb b/meta-oe/recipes-benchmark/fio/fio_3.7.bb
>>>> index 410e27b..9bec2df 100644
>>>> --- a/meta-oe/recipes-benchmark/fio/fio_3.7.bb
>>>> +++ b/meta-oe/recipes-benchmark/fio/fio_3.7.bb
>>>> @@ -32,6 +32,7 @@ S = "${WORKDIR}/git"
>>>> DISABLE_STATIC = ""
>>>>
>>>> EXTRA_OEMAKE = "CC='${CC}' LDFLAGS='${LDFLAGS}'"
>>>> +EXTRA_OECONF = "--disable-optimizations"
>>>>
>>>> do_configure() {
>>>> ./configure ${EXTRA_OECONF}
>>>> --
>>>> 2.7.4
>>>>
>>>> --
>>>> _______________________________________________
>>>> Openembedded-devel mailing list
>>>> Openembedded-devel@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>>
>
prev parent reply other threads:[~2018-08-21 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-20 9:41 [meta-oe][PATCH] fio: disable compiler optimizations mingli.yu
2018-08-21 7:19 ` Khem Raj
2018-08-21 7:19 ` Yu, Mingli
2018-08-21 7:24 ` Khem Raj
2018-08-21 7:25 ` Yu, Mingli [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=5B7BBE55.3000107@windriver.com \
--to=mingli.yu@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@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