tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] const_wanted


From: Thomas Preud'homme
Subject: Re: [Tinycc-devel] const_wanted
Date: Sun, 31 Jul 2011 17:05:49 +0200
User-agent: KMail/1.13.7 (Linux/3.0.0-1-amd64; KDE/4.6.5; x86_64; ; )

Le dimanche 31 juillet 2011 16:27:57, grischka a écrit :
> Thomas Preud'homme wrote:
> >> Can you show an example where this happens, that is that
> >> 
> >>     const_wanted is false
> >> 
> >> and
> >> 
> >>     cur_text_section is NULL
> >> 
> >> at the same time in cond_expr()?
> > 
> > Sure. It's a side effect of the VLA array patches. On Hurd, there is a
> > header with something like:
> > 
> > #define FOO_COUNT (cond ? 2 : 42)
> > 
> > type foo_array[FOO_SIZE];
> > 
> > This lead post_type to call gexpr() which will eventually call
> > cond_expr() without const_wanted. This in turn will try to generate some
> > code but will segfault due to cur_text_section being NULL (this is how I
> > spotted it, it caused a segfault in the testsuite on Hurd)
> 
> I still cannot reproduce this.  Can you show a self contained
> example to exhibit the bug?
Mmmmh good point, I should have tried with mob. I can't reproduce it neither. 
So I guess master is not as close to mob as I thought. I revert the patch 
immediately and keep it in Debian (it's only use in Debian experimental) until 
I found which patch fixed (or hide) the issue (it's not gonna be easy since I 
heard git is not available on Hurd so no git bisect).

Best regards,

Thomas Preud'homme
> 
> --- grischka
> 
> > I can give you the exact content of the header on Hurd if you need.
> > 
> > Best regards,
> > 
> > Thomas Preud'homme

Attachment: signature.asc
Description: This is a digitally signed message part.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]