public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/17627] M68060 fails with libstdc++-v3/config/cpu/m68k/atomicity.h
Date: Wed, 03 Nov 2004 22:25:00 -0000 [thread overview]
Message-ID: <20041103222514.12502.qmail@sourceware.org> (raw)
In-Reply-To: <20040923035910.17627.cjohns@cybertec.com.au>
------- Additional Comments From schwab at suse dot de 2004-11-03 22:25 -------
On the m68k the biggest alignment has traditionally only been 2 bytes
(inherited from the Sun compiler, AFAIK), and it's only overridden on NetBSD
(and previously on some configurations that are removed now) or when using
-malign-int. So unless you change that (which of course changes the ABI)
you'll continue to get unaligned long words somewhere.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17627
next prev parent reply other threads:[~2004-11-03 22:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 3:59 [Bug libstdc++/17627] New: " cjohns at cybertec dot com dot au
2004-09-23 8:59 ` [Bug libstdc++/17627] " schwab at suse dot de
2004-09-23 9:00 ` schwab at suse dot de
2004-09-23 10:20 ` cjohns at cybertec dot com dot au
2004-09-23 11:14 ` joel at oarcorp dot com
2004-09-23 16:40 ` pinskia at gcc dot gnu dot org
2004-11-01 20:02 ` bkoz at gcc dot gnu dot org
2004-11-02 12:28 ` joel at gcc dot gnu dot org
2004-11-02 23:57 ` cvs-commit at gcc dot gnu dot org
2004-11-03 0:12 ` bkoz at gcc dot gnu dot org
2004-11-03 21:09 ` joel at oarcorp dot com
2004-11-03 22:25 ` schwab at suse dot de [this message]
2004-11-03 22:56 ` joel at oarcorp dot com
2004-11-03 23:05 ` cjohns at cybertec dot com dot au
2004-11-03 23:25 ` joel at oarcorp dot com
2004-11-03 23:45 ` schwab at suse dot de
2004-11-04 2:17 ` peter at the-baradas dot com
2004-11-04 14:56 ` joel at oarcorp dot com
2004-11-04 15:12 ` schwab at suse dot de
2004-11-04 16:37 ` joel at oarcorp dot com
2004-11-04 16:53 ` schwab at suse dot de
2004-11-04 19:11 ` joel at oarcorp dot com
2005-02-07 17:41 ` pinskia at gcc dot gnu dot org
2005-02-07 18:53 ` cjohns at cybertec dot com dot au
2005-08-17 3:19 ` pinskia at gcc dot gnu dot 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=20041103222514.12502.qmail@sourceware.org \
--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).