public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/19388] [4.0 Regression] MAX_OFILE_ALIGNMENT on PA HP-UX
Date: Wed, 12 Jan 2005 02:53:00 -0000 [thread overview]
Message-ID: <20050112025355.28262.qmail@sourceware.org> (raw)
In-Reply-To: <20050112022518.19388.danglin@gcc.gnu.org>
------- Additional Comments From dave at hiauly1 dot hia dot nrc dot ca 2005-01-12 02:53 -------
Subject: Re: [4.0 Regression] MAX_OFILE_ALIGNMENT on PA HP-UX
> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-12
> 02:32 -------
> Hmm, I think pa abose of the macro really is the cause, maybe we should
> change the macro to
> dependent on the decl and then force the explicat use in the pa back-end so
> we don't run into this
> again?
I certainly agree that I abused the macro. However, many people were
using the alignment attribute to request alignments that the linker
wasn't capable of providing without -fno-common. This is critical for
when the decl is used for a semaphore lock. They require 16-byte
alignment on the PA. Also, I believe -fno-common only applies to C.
Thus, I think the above suggestion is a good one but the ada routine
doesn't have access to the decl. The only other solution that I can
see is to give up using common for uninitialized data.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19388
next prev parent reply other threads:[~2005-01-12 2:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 2:25 [Bug ada/19388] New: " danglin at gcc dot gnu dot org
2005-01-12 2:32 ` [Bug ada/19388] " pinskia at gcc dot gnu dot org
2005-01-12 2:53 ` dave at hiauly1 dot hia dot nrc dot ca [this message]
2005-01-15 17:10 ` cvs-commit at gcc dot gnu dot org
2005-01-15 18:21 ` [Bug target/19388] " 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=20050112025355.28262.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).