public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] libstdc++: ppc: conditionalize vsx-only simd intrinsics
Date: Mon, 2 May 2022 16:36:19 -0500	[thread overview]
Message-ID: <20220502213619.GW25951@gate.crashing.org> (raw)
In-Reply-To: <ormtg47izf.fsf@lxoliva.fsfla.org>

Hi!

On Thu, Apr 28, 2022 at 10:53:40PM -0300, Alexandre Oliva wrote:
> On Apr 28, 2022, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > On Thu, Apr 28, 2022 at 03:09:54AM -0300, Alexandre Oliva wrote:
> >> +		  "no __intrinsic_type support for [long] double on PPC w/o VSX");
> > This change isn't in the changelog.
> 
> It is, it's just that long double is dealt with differently from the
> other types, so requiring VSX for it takes a different form:

It changes a diagnostic message.  Incorrectly, even.  The changelog does
not talk about this.

The only thing I use changelogs for nowadays is to help reviewing code.
So when things are missing it stands out like a sore thumb.

> > 	* include/experimental/bits/simd.h [__ALTIVEC__]: Require VSX
> > 	for double, long long, and 64-bit long and 64-bit long double
> > 	intrinsic types.                           ^^^^^^^^^^^^^^^^^^

Yes, that does not talk about changing a diagnostic message.

> > The message should not say "long
> > double" without qualifying it as "64-bit long double".
> 
> How about qualifying both such messages as in this incremental patchlet:

Send full patches always please.  Not patches relative to some
non-existing state :-)

Thanks,


Segher

  parent reply	other threads:[~2022-05-02 21:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  6:09 Alexandre Oliva
2022-04-28 13:03 ` Segher Boessenkool
2022-04-29  1:53   ` Alexandre Oliva
2022-04-29 18:44     ` Matthias Kretz
2022-05-02 21:36     ` Segher Boessenkool [this message]
2022-05-03  2:00       ` [PATCH v2] " Alexandre Oliva
2022-05-06 16:14         ` Segher Boessenkool
2022-05-06 17:05           ` Jonathan Wakely
2022-05-06 18:24             ` [PATCH v3] " Alexandre Oliva
2022-04-28 13:56 ` [PATCH] " Matthias Kretz
2022-04-28 16:06   ` Segher Boessenkool

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=20220502213619.GW25951@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=oliva@adacore.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).