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: Mon, 01 Nov 2010 18:51:00 -0000	[thread overview]
Message-ID: <20101101185100.MP0XmmdX79wxzVSLwg6OuzXTCtmr-J-jLdSd740lj3E@z> (raw)
In-Reply-To: <bug-12123-131@http.sourceware.org/bugzilla/>

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

--- Comment #23 from Lluís Batlle <viriketo at gmail dot com> 2010-11-01 18:51:14 UTC ---
(In reply to comment #22)
> This is a compiler issue.  Use a fixed compiler.  If someone can identify a
> change in the compiler which fixes the problem an appropriate check can be
> added.  But perhaps not.  My strstr.os seems not to need any compiler changes. 
>  It must be local changes of some sort and then there should also be a local
> gcc check.  In any case, nothing to be done to the code, it's fine.

I think that all gccs previous to gcc 4.4 lack the configurable feature of
"expecting a stack alignment of X", that in gcc 4.4 due to the flags set in
glibc end up in "expecting a stack alignment of 2 words" - the behaviour
needed.
As other people in the bug report mentioned, that code (plus gcc flags) is
meant to be built only with gcc 4.4 or above.
You may name gcc 4.4 and above "a fixed compiler", but I would not say that
relates to any "local changes".

-- 
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-11-01 18:51 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
2010-11-01 18:42 ` drepper.fsp at gmail dot com
2010-11-01 18:51 ` viriketo at gmail dot com [this message]
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=20101101185100.MP0XmmdX79wxzVSLwg6OuzXTCtmr-J-jLdSd740lj3E@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).