public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jan.boon at kaetemi dot be" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/53758] New: Segfault at 'vmovaps' when setting pointer array in a loop
Date: Sun, 24 Jun 2012 08:42:00 -0000	[thread overview]
Message-ID: <bug-53758-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53758

             Bug #: 53758
           Summary: Segfault at 'vmovaps' when setting pointer array in a
                    loop
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jan.boon@kaetemi.be


Created attachment 27692
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27692
Disassemly of function and list of registers.

Segfault in a simple loop that sets pointers in an array to NULL.
Target is -march=bdver1 -mtune=bdver1.

for(i = 0; i < NL_DLM_LIGHTMAP_TYPE_SIZE; i++)
{
    _FreeBlocks[i] = NULL;
}

   0x00007ffff6ea4b00 <+608>:    inc    %edx
=> 0x00007ffff6ea4b02 <+610>:    vmovaps %xmm0,(%rcx)
   0x00007ffff6ea4b06 <+614>:    add    $0x10,%rcx
   0x00007ffff6ea4b0a <+618>:    cmp    %edx,%esi
   0x00007ffff6ea4b0c <+620>:    ja     0x7ffff6ea4b00 

edx            0x1    1
rcx            0x159106a4    361825956
esi            0x8    8

Full log in attachment.


             reply	other threads:[~2012-06-24  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-24  8:42 jan.boon at kaetemi dot be [this message]
2012-06-24 14:29 ` [Bug target/53758] " hjl.tools at gmail dot com
2012-06-24 17:07 ` jan.boon at kaetemi dot be

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=bug-53758-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).