public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "viriketo 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: Thu, 28 Oct 2010 20:10:00 -0000 [thread overview]
Message-ID: <20101028201000.lSd_vqSZHzRz5DCN4anLojpr0mh6wndsem0QTgP4TJs@z> (raw)
In-Reply-To: <bug-12123-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12123
--- Comment #20 from Lluís Batlle <viriketo at gmail dot com> 2010-10-28 20:10:04 UTC ---
(In reply to comment #19)
> (In reply to comment #18)
> > (In reply to comment #15)
> > > strstr.os was compiled with -mpreferred-stack-boundary=2 which implies
> > > -mincoming-stack-boundary=2, so it is a compiler bug if it assumes bigger
> > > alignment.
> >
> > I see '-mincoming-stack-boundary' appears only in gcc 4.4. Is gcc 4.4 a
> > requirement for building glibc?
> >
> > (In reply to comment #17)
> > We use gcc 4.3 to build glibc in i686-linux, and we use gcc 4.5.1 to build
>
> You need gcc 4.4 or above to properly align the stack in 32bit.
Ok, thank you. I see.
I tried building glibc with gcc 4.5.1, and strstr_sse42 starts properly:
1121d0: 55 push %ebp
1121d1: 89 e5 mov %esp,%ebp
1121d3: 83 e4 f0 and $0xfffffff0,%esp
Couldn't the configure script check the gcc version? Otherwise gcc 4.3 silently
builds a broken glibc.
--
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.
next prev parent reply other threads:[~2010-10-28 20:10 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 [this message]
2010-10-29 15:43 ` throctukes at gmail dot com
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=20101028201000.lSd_vqSZHzRz5DCN4anLojpr0mh6wndsem0QTgP4TJs@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).