public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64798] [5 regression] g++.old-deja/g++.eh/badalloc1.C FAILs
Date: Tue, 27 Jan 2015 12:51:00 -0000 [thread overview]
Message-ID: <bug-64798-4-aJ498t0Ggr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64798-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64798
--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 27 Jan 2015, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64798
>
> --- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I
> think aligned attribute is similarly useless for this, I'd really go for
> testing alignments you need, rather than expecting some magic value.
> I'm not aware of any target that would have bigger alignment for say
> char/short/int/long than long long, ditto with float/double, so I'd just
> check maximum of long long, long double, void * alignment.
For the actual bug I can use __alignof__ (__cxa_refcounted_exception),
but that again ends up using __attribute__((__aligned__)) via the
_Unwind_Exception member:
struct _Unwind_Exception
{
_Unwind_Exception_Class exception_class;
_Unwind_Exception_Cleanup_Fn exception_cleanup;
#if !defined (__USING_SJLJ_EXCEPTIONS__) && defined (__SEH__)
_Unwind_Word private_[6];
#else
_Unwind_Word private_1;
_Unwind_Word private_2;
#endif
/* @@@ The IA-64 ABI says that this structure must be double-word
aligned.
Taking that literally does not make much sense generically. Instead
we
provide the maximum alignment required by any type for the machine.
*/
} __attribute__((__aligned__));
so I think that using __attribute__((__aligned__)) is very much the
correct and easiest thing to use.
next prev parent reply other threads:[~2015-01-27 12:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:52 [Bug libstdc++/64798] New: " ro at gcc dot gnu.org
2015-01-26 13:53 ` [Bug libstdc++/64798] " ro at gcc dot gnu.org
2015-01-26 15:00 ` rguenther at suse dot de
2015-01-26 15:02 ` rguenther at suse dot de
2015-01-26 15:23 ` rguenth at gcc dot gnu.org
2015-01-26 15:45 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-01-27 10:58 ` rguenth at gcc dot gnu.org
2015-01-27 12:10 ` jakub at gcc dot gnu.org
2015-01-27 12:16 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-01-27 12:27 ` rguenther at suse dot de
2015-01-27 12:31 ` rguenth at gcc dot gnu.org
2015-01-27 12:33 ` jakub at gcc dot gnu.org
2015-01-27 12:38 ` rguenther at suse dot de
2015-01-27 12:40 ` rguenth at gcc dot gnu.org
2015-01-27 12:42 ` jakub at gcc dot gnu.org
2015-01-27 12:51 ` rguenther at suse dot de [this message]
2015-01-27 12:52 ` jakub at gcc dot gnu.org
2015-01-28 9:54 ` rguenth at gcc dot gnu.org
2015-01-28 10:01 ` rguenth at gcc dot gnu.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=bug-64798-4-aJ498t0Ggr@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).