From: Jeff Law <law@redhat.com>
To: Michael Meissner <meissner@linux.vnet.ibm.com>,
gcc-patches@gcc.gnu.org,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: Re: [PATCH], Simplify setup of complex types
Date: Tue, 21 Jun 2016 20:02:00 -0000 [thread overview]
Message-ID: <b076c019-a002-2b82-04a9-d4da7f9737c7@redhat.com> (raw)
In-Reply-To: <20160621134817.GA18335@ibm-tiger.the-meissners.org>
On 06/21/2016 07:48 AM, Michael Meissner wrote:
> When I submitted the back port to allow complex __float128 to be created on the
> PowerPC to the GCC 6.2 branch, Richard Biener suggested a simpler way to set
> the complex type:
> https://gcc.gnu.org/ml/gcc-patches/2016-06/msg01114.html
>
> This patch implements this change for the trunk. I have a companion patch for
> 6.2 once this goes into the trunk.
>
> I bootstrapped the compiler and did a make check with no regressions on a big
> endian Power 7 system and a little endian Power 8 system. Is it ok to go into
> the trunk?
>
> [gcc]
> 2016-06-21 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> * stor-layout.c (layout_type): Move setting complex MODE to
> layout_type, instead of setting it ahead of time by the caller.
> * tree.c (build_complex_type): Likewise.
>
> [gcc/fortran]
> 2016-06-21 Michael Meissner <meissner@linux.vnet.ibm.com>
>
> * trans-types.c (gfc_build_complex_type): Move setting complex
> MODE to layout_type, instead of setting it ahead of time by the
> caller.
OK.
Jeff
ps. Thanks for the pointer back to the prior discussion with Richi --
that makes it a lot easier to pick up state on this while Richi is on PTO.
prev parent reply other threads:[~2016-06-21 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 13:48 Michael Meissner
2016-06-21 20:02 ` Jeff Law [this message]
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=b076c019-a002-2b82-04a9-d4da7f9737c7@redhat.com \
--to=law@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.vnet.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.vnet.ibm.com \
/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).