public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davem at davemloft dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59758] [4.9/4.10 Regression] bootstrap failure in libsanitizer/asan on sparc-linux-gnu
Date: Fri, 02 May 2014 06:12:00 -0000	[thread overview]
Message-ID: <bug-59758-4-khwStKITSK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59758-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from David S. Miller <davem at davemloft dot net> ---
The next problem you'll run into is that the shmid additions for sparc weren't
done correctly in the patch.  Where you see 's64', it should be 'long', and
where you see 'u64' it should be 'unsigned long'.

I strongly suspect the patch was only build tested on 64-bit, as all of the
mistakes in the patch are for 32-bit cases.


  parent reply	other threads:[~2014-05-02  6:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 14:15 [Bug sanitizer/59758] New: [4.9 " doko at gcc dot gnu.org
2014-01-13 10:01 ` [Bug sanitizer/59758] " rguenth at gcc dot gnu.org
2014-01-13 10:11 ` jakub at gcc dot gnu.org
2014-01-13 10:23 ` jakub at gcc dot gnu.org
2014-02-18 12:28 ` jose.marchesi at oracle dot com
2014-02-18 18:29 ` jose.marchesi at oracle dot com
2014-02-18 23:20 ` ebotcazou at gcc dot gnu.org
2014-04-12 19:44 ` [Bug sanitizer/59758] [4.9/4.10 " aaro.koskinen at iki dot fi
2014-04-22 11:37 ` jakub at gcc dot gnu.org
2014-05-02  5:56 ` davem at davemloft dot net
2014-05-02  6:12 ` davem at davemloft dot net [this message]
2014-05-02  6:24 ` davem at davemloft dot net
2014-07-16 13:30 ` jakub at gcc dot gnu.org
2014-10-10 18:44 ` [Bug sanitizer/59758] [4.9/5 " rth at gcc dot gnu.org
2014-10-14 21:24 ` davem at gcc dot gnu.org

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-59758-4-khwStKITSK@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).