From: Christopher Li <sparse@chrisli.org>
To: Michael Stefaniuc <mstefani@mykolab.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Re: Infinite loop with OOM while testing Sparse on Wine code
Date: Tue, 18 Jul 2017 13:11:14 -0400 [thread overview]
Message-ID: <CANeU7QkGeMuX7hjfxw-3Mi1_urmBS8znrxRO0VFp5Q+gh7FPTQ@mail.gmail.com> (raw)
In-Reply-To: <a4d23510-5bd4-9d88-f7a8-731882744043@mykolab.com>
On Tue, Jul 18, 2017 at 10:47 AM, Michael Stefaniuc
<mstefani@mykolab.com> wrote:
>
> make[1]: Entering directory '/j/wine/build/sparse64/dlls/user32/tests'
> cgcc -c -o menu.o /home/michi/work/wine/dlls/user32/tests/menu.c -I. \
> -I/home/michi/work/wine/dlls/user32/tests -I../../../include
> -I/home/michi/work/wine/include \
> -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing
> -Wdeclaration-after-statement \
> -Wempty-body -Wignored-qualifiers -Wshift-overflow=2
> -Wstrict-prototypes -Wtype-limits \
> -Wunused-but-set-parameter -Wvla -Wwrite-strings -Wpointer-arith
> -Wlogical-op -gdwarf-2 \
> -gstrict-dwarf -g -O2
Adding CC of Luc,
It is much easier to reproduce the error from the command line as above.
Just update the wine directory name is good enough for me.
I can see how it is loop on the CSE phase. It is trying to simplify the
set_ne constant follow by a branch. However it did not change the
instruction and keep setting the CSE flag. Need more digging.
My gut feeling is that we should fix this before the release.
Chris
next prev parent reply other threads:[~2017-07-18 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 14:47 Infinite loop with OOM while testing Sparse on Wine code Michael Stefaniuc
2017-07-18 15:11 ` Christopher Li
2017-07-18 17:11 ` Christopher Li [this message]
2017-07-18 23:12 ` Christopher Li
2017-07-19 0:07 ` Christopher Li
2017-07-19 13:26 ` Christopher Li
2017-07-19 15:25 ` Christopher Li
2017-07-19 18:50 ` Michael Stefaniuc
2017-07-19 20:43 ` Luc Van Oostenryck
2017-07-19 21:16 ` Christopher Li
2017-07-20 22:44 ` Luc Van Oostenryck
2017-07-26 17:29 ` Christopher Li
2017-07-29 14:39 ` Luc Van Oostenryck
2017-07-29 20:05 ` Christopher Li
2017-07-29 23:38 ` Luc Van Oostenryck
2017-07-29 23:58 ` [PATCH] fix: try_to_simplify_bb eargerness part 2 Luc Van Oostenryck
2017-07-30 15:38 ` Christopher Li
2017-07-30 16:04 ` Luc Van Oostenryck
2017-07-30 17:06 ` Christopher Li
2017-07-30 0:01 ` Infinite loop with OOM while testing Sparse on Wine code Luc Van Oostenryck
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=CANeU7QkGeMuX7hjfxw-3Mi1_urmBS8znrxRO0VFp5Q+gh7FPTQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mstefani@mykolab.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;
as well as URLs for NNTP newsgroup(s).