* Seg fault in linearizer after latest patch series
@ 2017-03-16 0:24 Dibyendu Majumdar
2017-03-16 0:30 ` Dibyendu Majumdar
2017-03-16 16:30 ` Luc Van Oostenryck
0 siblings, 2 replies; 3+ messages in thread
From: Dibyendu Majumdar @ 2017-03-16 0:24 UTC (permalink / raw)
To: Linux-Sparse
Hi Luc,
I am getting a segmentation fault in the linearizer - which I
replicated using your GitHub repository branch llvm-fixes-v2.
Please try -v option when running test-linearizer on this program.
Other programs also cause this. Looks like the offending line is
accessing the def field in a pseudo - and I think one of your recent
changes does not set def anymore?
static double test(double *p)
{
double x;
x = *p;
return x;
}
int main(void)
{
double u,v;
v = 42.0;
u = test(&v);
return v;
}
Thanks and Regards
Dibyendu
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Seg fault in linearizer after latest patch series
2017-03-16 0:24 Seg fault in linearizer after latest patch series Dibyendu Majumdar
@ 2017-03-16 0:30 ` Dibyendu Majumdar
2017-03-16 16:30 ` Luc Van Oostenryck
1 sibling, 0 replies; 3+ messages in thread
From: Dibyendu Majumdar @ 2017-03-16 0:30 UTC (permalink / raw)
To: Linux-Sparse
On 16 March 2017 at 00:24, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> Hi Luc,
>
> I am getting a segmentation fault in the linearizer - which I
> replicated using your GitHub repository branch llvm-fixes-v2.
>
> Please try -v option when running test-linearizer on this program.
> Other programs also cause this. Looks like the offending line is
> accessing the def field in a pseudo - and I think one of your recent
> changes does not set def anymore?
>
Sorry I mean above that it does set def in argument pseudos. So
perhaps a chek is needed when there is an attempt to access def.
Regards
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Seg fault in linearizer after latest patch series
2017-03-16 0:24 Seg fault in linearizer after latest patch series Dibyendu Majumdar
2017-03-16 0:30 ` Dibyendu Majumdar
@ 2017-03-16 16:30 ` Luc Van Oostenryck
1 sibling, 0 replies; 3+ messages in thread
From: Luc Van Oostenryck @ 2017-03-16 16:30 UTC (permalink / raw)
To: Dibyendu Majumdar; +Cc: Linux-Sparse
On Thu, Mar 16, 2017 at 12:24:03AM +0000, Dibyendu Majumdar wrote:
> Hi Luc,
>
> I am getting a segmentation fault in the linearizer - which I
> replicated using your GitHub repository branch llvm-fixes-v2.
>
> Please try -v option when running test-linearizer on this program.
> Other programs also cause this. Looks like the offending line is
> accessing the def field in a pseudo - and I think one of your recent
> changes does not set def anymore?
>
> static double test(double *p)
> {
> double x;
> x = *p;
> return x;
> }
> int main(void)
> {
>
> double u,v;
> v = 42.0;
> u = test(&v);
> return v;
> }
Hi,
Yes, there is several such crashes that may arise with the -v option,
I mean, even without the llvm serie.
I've a trivial patch for some of the cases since a little while,
I just need a bit more time.
Luc
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-03-16 16:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-16 0:24 Seg fault in linearizer after latest patch series Dibyendu Majumdar
2017-03-16 0:30 ` Dibyendu Majumdar
2017-03-16 16:30 ` Luc Van Oostenryck
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.