public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/56897] unaligned memory access on alpha
Date: Tue, 16 Apr 2013 15:15:00 -0000	[thread overview]
Message-ID: <bug-56897-4-EAV78hvEeE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56897-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #7 from Uros Bizjak <ubizjak at gmail dot com> 2013-04-16 15:15:14 UTC ---
(In reply to comment #4)
> Hi,
> 
> (In reply to comment #3)
> > Please create a self-sufficient executable testcase, following the instructions
> > at [1]. I was not able to confirm the problem from the lines you posted.
> 
> Thanks for the feedback, Uros.  Did you try it together with the frame 
> growing downwards diff posted in #56898?  If so, the locals are actually
> at the negative offsets and unaligned loads like foo%8-5 will expose this,
> instead of foo%8-1.

No, I am using unpatched compiler. Compiling your ab-pre.tgz test, I got:

~/gcc-build-47/gcc/xgcc -B ~/gcc-build-47/gcc -O a.c
uros@monolith ~/test $ ./a.out
0d0a
0d0a0401
0d0a0401

~/gcc-build-47/gcc/xgcc -B ~/gcc-build-47/gcc -O -mcpu=ev4 a.c
uros@monolith ~/test $ ./a.out
0d0a
0d0a0401
0d0a0401

with:

GNU C (GCC) version 4.7.3 20130228 (prerelease) [gcc-4_7-branch revision
196343] (alphaev68-unknown-linux-gnu)

and the same result (with the same flags) with:

GNU C (GCC) version 4.9.0 20130407 (experimental) [trunk revision 197551]
(alphaev68-unknown-linux-gnu)

The compilers imply -mcpu=ev67 when invoked without -mcpu command.


      parent reply	other threads:[~2013-04-16 15:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  3:53 [Bug target/56897] New: " martynas at venck dot us
2013-04-10  3:55 ` [Bug target/56897] " martynas at venck dot us
2013-04-10  6:43 ` ubizjak at gmail dot com
2013-04-15  7:54 ` ubizjak at gmail dot com
2013-04-16  4:11 ` martynas at venck dot us
2013-04-16  4:16 ` martynas at venck dot us
2013-04-16  4:18 ` martynas at venck dot us
2013-04-16 15:15 ` ubizjak at gmail dot com [this message]

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-56897-4-EAV78hvEeE@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).