From: Bob Dunlop <bob.dunlop@xyzzy.org.uk>
To: crossgcc@sourceware.org
Subject: Re: Compiler Memory Alignment Issue
Date: Fri, 03 Feb 2012 10:16:00 -0000 [thread overview]
Message-ID: <20120203101627.GA13646@xyzzy.org.uk> (raw)
In-Reply-To: <SNT112-W20026C65DA2489BC8955CE87700@phx.gbl>
On Thu, Feb 02 at 01:15, Richard Koch wrote:
>
> Hello List,
>
> I'm seeing an alignment issue when I'm incrementing a pointer.
...
It's not specifically ct-ng at fault but the compiler.
I can reproduce the problem if I build Gcc 3.3.3 but not with my regular
build (4.4.4).
> I'm wondering if there may be something I haven't set properly in the crosstool-ng's
> configuration?
Try a more recent compiler version.
--
Bob Dunlop
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2012-02-03 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 18:15 Richard Koch
2012-02-02 23:09 ` Martin Guy
2012-02-02 23:26 ` Rod Nussbaumer
2012-02-03 9:52 ` Martin Guy
2012-02-03 10:16 ` Bob Dunlop [this message]
2012-02-03 13:21 ` Yann E. MORIN
2012-02-03 14:14 ` Johannes Stezenbach
2012-02-03 14:23 ` Yann E. MORIN
2012-02-03 20:41 ` Johannes Stezenbach
2012-02-03 15:13 ` Richard Koch
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=20120203101627.GA13646@xyzzy.org.uk \
--to=bob.dunlop@xyzzy.org.uk \
--cc=crossgcc@sourceware.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).