public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mcvick_e at iname dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/23539] C & C++ compiler generating misaligned references regardless of compiler flags
Date: Wed, 24 Aug 2005 00:28:00 -0000 [thread overview]
Message-ID: <20050824002037.18536.qmail@sourceware.org> (raw)
In-Reply-To: <20050823212148.23539.mcvick_e@iname.com>
------- Additional Comments From mcvick_e at iname dot com 2005-08-24 00:20 -------
Unfortunately this still appears to be some sort of bug. The solution given
with the -mstrict-align worked for the test case, but in the specific case
here, still fails. Attached is the output of the link command given. The
compiler invocation for all of the associated files that make the libraries,
and object files all contain the -mstrict-align.
See the text below...
(1)> ppcg++ -gstabs+ -O1 -fno-guess-branch-probability -mcpu=603e -mtune=603e -
mstrict-align -nostdlib -DGH_COMPAT -DAVOID_EMPTY_CLASSES -DSVRT_TRACE -fno-use-
cxa-atexit -fcheck-new -fno-rtti -fno-exceptions -Wabi -
Wextra /export/GNU_port/MM.1/lib/sac/begin.o /export/GNU_port/MM.1/lib/sac/sysin
it.o /export/GNU_port/MM.1/lib/sac/prepccfg.o /export/GNU_port/MM.1/lib/sac/psos
cfg.o /export/GNU_port/MM.1/lib/sac/drv_conf.o --no-undefined -Bstatic --warn-
section-align --demangle --warn-once --warn-common --sort-common -T sac.cmd -
L /export/GNU_port/MM.1/lib -L /export/GNU_port/MM.1/lbcs/lib \
-o /export/GNU_port/MM.1/bins/sac.x
-------------------------------------------------------------------
(2)> ppcobjdump -C -S sac.x | grep sth | less
494108: b3 43 00 18 sth r26,24(r3)
49410c: b3 23 00 1a sth r25,26(r3)
494110: b3 03 00 1c sth r24,28(r3)
494c0c: b0 01 00 21 sth r0,33(r1) <-- Still ODD alignment
4954a0: b1 3a 30 ec sth r9,12524(r26)
4956ac: b1 23 00 04 sth r9,4(r3)
4957d4: b0 03 00 a4 sth r0,164(r3)
4959a8: b1 23 00 00 sth r9,0(r3)
495bac: b0 03 00 a4 sth r0,164(r3)
495ed0: b1 2a 30 e0 sth r9,12512(r10)
(3)>
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23539
next prev parent reply other threads:[~2005-08-24 0:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 21:23 [Bug c++/23539] New: " mcvick_e at iname dot com
2005-08-23 21:30 ` [Bug target/23539] " pinskia at gcc dot gnu dot org
2005-08-23 22:24 ` mcvick_e at iname dot com
2005-08-23 22:30 ` mcvick_e at iname dot com
2005-08-23 23:05 ` pinskia at gcc dot gnu dot org
2005-08-23 23:35 ` steven at gcc dot gnu dot org
2005-08-24 0:20 ` mcvick_e at iname dot com
2005-08-24 0:28 ` mcvick_e at iname dot com [this message]
2005-08-24 0:40 ` pinskia at gcc dot gnu dot org
2005-08-24 3:53 ` mcvick_e at iname dot com
2005-08-24 16:00 ` mcvick_e at iname dot com
2005-08-26 23:56 ` dje at gcc dot gnu dot org
2005-08-27 0:11 ` dje at gcc dot gnu dot org
2005-08-27 15:46 ` cvs-commit at gcc dot gnu dot org
2005-08-27 16:59 ` cvs-commit at gcc dot gnu dot org
2005-08-31 14:31 ` cvs-commit at gcc dot gnu dot org
2005-08-31 15:08 ` dje 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=20050824002037.18536.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).