public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "throctukes at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/12123] SIGBUS on strstr_sse42 due to bad alignment
Date: Fri, 29 Oct 2010 15:43:00 -0000	[thread overview]
Message-ID: <20101029154300.57Bg6Zwi0h1iPRCd7t7cQbna2fmMxppV-RcckOesIbo@z> (raw)
In-Reply-To: <bug-12123-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=12123

--- Comment #21 from throctukes at gmail dot com 2010-10-29 15:43:28 UTC ---
(In reply to comment #18)
> We use gcc 4.3 to build glibc in i686-linux, and we use gcc 4.5.1 to build
> x86_64-linux, so that may make a difference, and maybe that's why we only saw
> the problem in i686-linux. What compiler are you using?
> With gcc 4.5.1, strstr_sse42 starts this way:
>  130:   48 89 5c 24 d0          mov    %rbx,-0x30(%rsp)
>  135:   4c 89 6c 24 e8          mov    %r13,-0x18(%rsp)
>  13a:   48 89 fb                mov    %rdi,%rbx
>  13d:   48 89 6c 24 d8          mov    %rbp,-0x28(%rsp)
>  142:   4c 89 64 24 e0          mov    %r12,-0x20(%rsp)
>  147:   49 89 f5                mov    %rsi,%r13
>  14a:   4c 89 74 24 f0          mov    %r14,-0x10(%rsp)
>  14f:   4c 89 7c 24 f8          mov    %r15,-0x8(%rsp)
>  154:   48 83 ec 58             sub    $0x58,%rsp
> 
> So it expects stacks 4w aligned, the default in gcc. If you have problems in
> x86_64 about bad alignment on strstr_sse42, you should revise that your code
> maintains the stack aligned 4w.

I've been using the libc6 from the Ubuntu repositories, but even recompiling
glibc from sources with gcc 4.4 and 4.5 makes no difference.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2010-10-29 15:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14 20:42 [Bug libc/12123] New: " viriketo at gmail dot com
2010-10-14 20:43 ` [Bug libc/12123] " viriketo at gmail dot com
2010-10-26  3:02 ` drepper.fsp at gmail dot com
2010-10-26  6:46 ` hjl.tools at gmail dot com
2010-10-26  7:23 ` viriketo at gmail dot com
2010-10-26  7:39 ` hjl.tools at gmail dot com
2010-10-26  7:51 ` viriketo at gmail dot com
2010-10-26  7:52 ` viriketo at gmail dot com
2010-10-26 15:12 ` schwab@linux-m68k.org
2010-10-26 16:17 ` viriketo at gmail dot com
2010-10-26 16:31 ` viriketo at gmail dot com
2010-10-26 16:49 ` viriketo at gmail dot com
2010-10-26 17:22 ` hjl.tools at gmail dot com
2010-10-26 17:24 ` viriketo at gmail dot com
2010-10-26 17:37 ` jakub at redhat dot com
2010-10-26 17:53 ` viriketo at gmail dot com
2010-10-27  8:25 ` schwab@linux-m68k.org
2010-10-27 12:38 ` viriketo at gmail dot com
2010-10-28 15:42 ` throctukes at gmail dot com
2010-10-28 19:29 ` viriketo at gmail dot com
2010-10-28 19:32 ` hjl.tools at gmail dot com
2010-10-28 20:10 ` viriketo at gmail dot com
2010-10-29 15:43 ` throctukes at gmail dot com [this message]
2010-11-01 18:42 ` drepper.fsp at gmail dot com
2010-11-01 18:51 ` viriketo at gmail dot com
2014-06-30  7:49 ` fweimer at redhat dot com

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=20101029154300.57Bg6Zwi0h1iPRCd7t7cQbna2fmMxppV-RcckOesIbo@z \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).