public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bangerth@dealii.org To: dholm@telia.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: target/7582: Intel intrinsics cause segfault with gcc 3.1.1 and 3.2 Date: Sat, 11 Jan 2003 01:28:00 -0000 [thread overview] Message-ID: <20030111012810.24322.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2003-01-11 1:28 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-11 1:28 bangerth [this message] 2003-01-11 1:52 bangerth 2003-01-11 1:56 David Holm
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=20030111012810.24322.qmail@sources.redhat.com \ --to=bangerth@dealii.org \ --cc=dholm@telia.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).