public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Martitz <thomas.martitz@student.HTW-Berlin.de>
To: gcc-help@gcc.gnu.org
Subject: Re: Problems migrating to gcc 4.4.3&eabi  - apparently a gcc bug
Date: Tue, 09 Mar 2010 19:44:00 -0000	[thread overview]
Message-ID: <4B96A501.1000806@htw-berlin.de> (raw)
In-Reply-To: <C7BC0010.1A667%eljay@adobe.com>

Am 09.03.2010 20:39, schrieb John (Eljay) Love-Jensen:
> Hi Thomas,
>
> Is this a factor...?
>
> """
> Note that the effectiveness of aligned attributes may be limited by inherent
> limitations in your linker. On many systems, the linker is only able to
> arrange for variables to be aligned up to a certain maximum alignment. (For
> some linkers, the maximum supported alignment may be very very small.) If
> your linker is only able to align variables up to a maximum of 8 byte
> alignment, then specifying aligned(16) in an __attribute__ will still only
> provide you with 8 byte alignment. See your linker documentation for further
> information.
> """
>
> http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html
> http://gcc.gnu.org/onlinedocs/gcc/Type-Attributes.html
>
> Do you know if the linker being used supports the alignment your code is
> requesting on your platform?
>
> Sincerely,
> --Eljay
>
>    

It doesn't have anything to with the linker. The example code I posted 
shows the bug even before being linked or assembled.

And I'm not searching for help on aligning stuff, I'm searching for help 
regarding the buggy register allocation for subroutine calls.

Best regards.

  reply	other threads:[~2010-03-09 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 16:31 Thomas Martitz
2010-03-09 16:42 ` Andrew Haley
2010-03-09 17:11   ` Thomas Martitz
2010-03-09 18:36     ` Andrew Haley
2010-03-09 18:54       ` Thomas Martitz
2010-03-09 19:11         ` Thomas Martitz
2010-03-09 19:39           ` John (Eljay) Love-Jensen
2010-03-09 19:44             ` Thomas Martitz [this message]
2010-03-09 19:46         ` Andrew Haley
2010-03-10 15:56           ` Ian Lance Taylor
2010-03-10 16:36             ` Thomas Martitz

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=4B96A501.1000806@htw-berlin.de \
    --to=thomas.martitz@student.htw-berlin.de \
    --cc=gcc-help@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).