https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #13 from Jouko Orava ---
(In reply to Joost VandeVondele from comment #12)
> I'm wondering if you had a working patch at some point.
Not a comprehensive one, no. I recall modifying libgfortran/runtime/memory.c
was not sufficient.
I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
Joost VandeVondele changed:
What|Removed |Added
CC||Joost.VandeVondele at mat dot
ethz
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #11 from Jouko Orava ---
Just in case there are users who encounter this bug report,
here is the single-file workaround. Save the following as
nosegfault.c, and follow the instructions in the comments.
It can be compiled into a shared
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #10 from Jouko Orava ---
(In reply to Dominique d'Humieres from comment #9)
> I can do the testing on darwin (intel d10 and d13, ppc d9).
That would be very much appreciated.
I've put a tarball and some background info on my web page
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #9 from Dominique d'Humieres ---
> My hardware selection is very limited, but if someone wishes to test the
> possibilities on other hardware, I'd be happy to clean up my benchmarking
> code.
I can do the testing on darwin (intel d10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
Jouko Orava changed:
What|Removed |Added
CC||jouko.orava at iki dot fi
--- Comment #8 fr
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
Uroš Bizjak changed:
What|Removed |Added
CC||thatcadguy at gmail dot com
--- Comment #7
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #6 from joseph at codesourcery dot com 2013-01-09 20:57:13 UTC ---
On Wed, 9 Jan 2013, pinskia at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
>
> --- Comment #5 from Andrew Pinski 2013-01-09
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #5 from Andrew Pinski 2013-01-09
16:09:25 UTC ---
> As __float128 is outside of the scope of C/C++, this is not a bug on the C
> library side.
It might be outside the scope of C/C++ but doesn't C99 allow some
implementation
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #4 from Richard Biener 2013-01-09
13:38:12 UTC ---
(In reply to comment #3)
> (In reply to comment #2)
> > (In reply to comment #1)
> > > posix_memalign unfortunately has a weird enough interface that we can't
> > > easily ex
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
--- Comment #3 from Richard Biener 2013-01-09
13:30:27 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > posix_memalign unfortunately has a weird enough interface that we can't
> > easily extract alignment for the pointer.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
Marc Glisse changed:
What|Removed |Added
CC||glisse at gcc dot gnu.org
--- Com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55916
Richard Biener changed:
What|Removed |Added
Keywords||wrong-code
Status|U
13 matches
Mail list logo