public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: target/7582: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2
@ 2003-01-11 1:56 David Holm
0 siblings, 0 replies; 3+ messages in thread
From: David Holm @ 2003-01-11 1:56 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR target/7582; it has been noted by GNATS.
>From david@realityrift.com Mon Jan 13 00:56:22 2003
From: David Holm <david@realityrift.com>
To: bangerth@dealii.org, dholm@telia.com, gcc-bugs@gcc.gnu.org,
gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:
Subject: Re: target/7582: Intel intrinsics cause segfault with gcc 3.1.1 and
3.2
Date: Sat, 11 Jan 2003 02:48:44 +0100
I didn't find a function to close this report.
You can close it since the problem was that I though malloc would use __mm_alloc
//David Holm
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: target/7582: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2
@ 2003-01-11 1:52 bangerth
0 siblings, 0 replies; 3+ messages in thread
From: bangerth @ 2003-01-11 1:52 UTC (permalink / raw)
To: dholm, gcc-bugs, gcc-prs, nobody
Synopsis: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2
State-Changed-From-To: feedback->closed
State-Changed-By: bangerth
State-Changed-When: Fri Jan 10 17:52:37 2003
State-Changed-Why:
Closed on request of submitter.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7582
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: target/7582: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2
@ 2003-01-11 1:28 bangerth
0 siblings, 0 replies; 3+ messages in thread
From: bangerth @ 2003-01-11 1:28 UTC (permalink / raw)
To: dholm, gcc-bugs, gcc-prs, nobody
Synopsis: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2
State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Fri Jan 10 17:28:09 2003
State-Changed-Why:
I understand that this is not the most politely worded
question (taken from the audit trail of this report), but
could you nevertheless reply to it?
-----
You start off with no attempt to get aligned storage for tmp1 and tmp2. In
an ideal world, malloc would take care of this, but gcc doesn't take
responsibility for which malloc you use. I take it you are using whatever
glibc gives you. Mine gives me 8-byte alignment, but not the required
16-byte alignment. Since you didn't mention whether you stepped into
your code with your favorite debugger to check for such problems, some of us
may assume you haven't begun to do your homework. If you did use a strategy
to assure alignment, you haven't informed us what it might be.
You've gone out of your way to obscure your code, yet you ignore what seems
most evident.
As I understand it, the preference for the Intel compiler would be to use the
special aligned entry point _mm_malloc(), in order to make your code portable
to Windows, so you are lucky it works with icc.
-----
Thanks
Wolfgang
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7582
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-01-11 1:56 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-11 1:56 target/7582: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2 David Holm
-- strict thread matches above, loose matches on Subject: below --
2003-01-11 1:52 bangerth
2003-01-11 1:28 bangerth
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 read-only IMAP folder(s) and NNTP newsgroup(s).