From: John David Anglin <dave.anglin@bell.net>
To: Florian Weimer <fweimer@redhat.com>, Jeff Law <law@redhat.com>,
Jakub Jelinek <jakub@redhat.com>
Cc: Carlos O'Donell <carlos@redhat.com>,
Jason Merrill <jason@redhat.com>,
Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Implement new hook for max_align_t_align
Date: Wed, 12 Oct 2016 18:13:00 -0000 [thread overview]
Message-ID: <a91d4d0c-652d-6d60-0c78-efb8fdb018ec@bell.net> (raw)
In-Reply-To: <d4c5e6ef-134f-aa90-fc3b-ffb58c4da571@redhat.com>
On 2016-10-12 2:01 PM, Florian Weimer wrote:
> On 10/12/2016 06:14 PM, Jeff Law wrote:
>
>> If the issue is strictly limited to 32 bit hpux, then do we really care?
>> Can we just deprecate that platform and thus make the issue go away?
>
> Are we talking about HP-XX or Linux on PA-RISC?
The patch was intended to address a Linux issue on PA-RISC. On HP-UX,
the current
version of max_align_t is fine.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2016-10-12 18:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 17:01 Bernd Edlinger
2016-10-08 17:36 ` John David Anglin
2016-10-09 8:35 ` Bernd Edlinger
2016-10-09 17:52 ` John David Anglin
2016-10-10 18:21 ` John David Anglin
2016-10-11 18:51 ` Jason Merrill
2016-10-11 18:59 ` DJ Delorie
2016-10-11 20:12 ` Jason Merrill
2016-10-11 20:55 ` John David Anglin
2016-10-11 20:57 ` Jakub Jelinek
2016-10-11 21:27 ` Jason Merrill
2016-10-11 20:04 ` John David Anglin
2016-10-12 7:02 ` Carlos O'Donell
2016-10-12 7:25 ` Jakub Jelinek
2016-10-12 7:52 ` Florian Weimer
2016-10-12 8:02 ` Jakub Jelinek
2016-10-12 12:13 ` John David Anglin
2016-10-12 12:33 ` Bernd Schmidt
2016-10-12 12:43 ` Richard Biener
2016-10-12 12:46 ` Bernd Schmidt
2016-10-12 15:51 ` Joseph Myers
2016-10-12 13:48 ` Jason Merrill
2016-10-12 14:17 ` John David Anglin
2016-10-12 19:59 ` Carlos O'Donell
2016-10-12 16:14 ` Jeff Law
2016-10-12 17:24 ` John David Anglin
2017-02-25 17:46 ` Gerald Pfeifer
2017-02-25 22:13 ` John David Anglin
2017-02-25 22:46 ` Gerald Pfeifer
2017-02-25 23:46 ` John David Anglin
2016-10-12 18:01 ` Florian Weimer
2016-10-12 18:13 ` John David Anglin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-10-08 16:43 Bernd Edlinger
2016-10-08 15:45 John David Anglin
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=a91d4d0c-652d-6d60-0c78-efb8fdb018ec@bell.net \
--to=dave.anglin@bell.net \
--cc=bernd.edlinger@hotmail.de \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=law@redhat.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).