public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/102837] [12 regression] Many 32-bit gdc tests FAIL
Date: Mon, 25 Oct 2021 21:37:20 +0000 [thread overview]
Message-ID: <bug-102837-4-lLUeNr4Tkb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102837-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102837
ibuclaw at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ibuclaw at gcc dot gnu.org
--- Comment #4 from ibuclaw at gcc dot gnu.org ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #3)
> Actually, it's
>
> commit efa5449a094d3887e124d400ff0410af2c745b2d
> Author: Iain Buclaw <ibuclaw@gdcproject.org>
> Date: Sat Sep 25 19:50:52 2021 +0200
>
> libphobos: Give _Unwind_Exception an alignment that best resembles
> __attribute__((aligned))
>
> in particular
>
> +else version (X86) private enum __aligned__ = 16;
>
> I don't yet see where/how struct _Unwind_Execption is allocated to
> guarantee that alignment. Depending on the answer PR libstdc++/77691
> (32-bit Solaris/x86 malloc only returns 8-byte aligned memory) or the
> fact that the stack is only 4-byte aligned following the i386 psABI) may
> be relevant.
i386 psABI would likely be the most relevant detail here. I'll see if exposing
the value of __attribute__((aligned)) to D CTFE is possible.
next prev parent reply other threads:[~2021-10-25 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 12:36 [Bug d/102837] New: " ro at gcc dot gnu.org
2021-10-19 12:36 ` [Bug d/102837] " ro at gcc dot gnu.org
2021-10-19 19:28 ` pinskia at gcc dot gnu.org
2021-10-19 19:29 ` pinskia at gcc dot gnu.org
2021-10-25 11:32 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-10-25 21:37 ` ibuclaw at gcc dot gnu.org [this message]
2021-10-30 22:19 ` ibuclaw at gdcproject dot org
2021-10-31 18:52 ` cvs-commit at gcc dot gnu.org
2021-10-31 21:43 ` ibuclaw at gdcproject 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=bug-102837-4-lLUeNr4Tkb@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).