This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: arch-specific template code

From: Ulrich Drepper <drepper at gmail dot com>
To: Paolo Carlini <paolo dot carlini at oracle dot com>
Cc: libstdc++ at gcc dot gnu dot org, Jonathan Wakely <jwakely dot gcc at gmail dot com>
Date: Mon, 10 Sep 2012 05:38:29 -0400
Subject: Re: arch-specific template code
References: <CAOPLpQex7niqQ4VWoSheHpbb8-Jf9S+nULgxB3WNUp4r_xyriw@mail.gmail.com> <503BF427.1030300@oracle.com> <CAOPLpQdRUONpKZ9WfD1VP+YgmJVoJxp1L6OL=5hXH2LzjnZ8ww@mail.gmail.com> <504B0DAD.5000302@oracle.com> <CAOPLpQfHf9v0a_-nbsfcWWEvP4Hyf_cfRi5b8orfVfB2OcSrTQ@mail.gmail.com> <504DB2AB.1050608@oracle.com>

On Mon, Sep 10, 2012 at 5:28 AM, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> maybe we could handle first some of those
> straightforward cases which you presented earlier, which simply add
> __generate (double*, double*, ...)

I deliberately didn't do that.  A patch to just add specializations
could have added an #include to the end of <random> and <ext/random>
and be done.  What I wanted to show is that this is not sufficient.
The patch I submitted adds the infrastructure to handle the more
generic case as well as cleaning up the arch-specific code from a
generic header.  Just imagine if every architecture with vector
support adds their own code to the generic files.

Follow-Ups:
- Re: arch-specific template code
  - From: Paolo Carlini

References:
- Re: arch-specific template code
  - From: Paolo Carlini
- Re: arch-specific template code
  - From: Ulrich Drepper
- Re: arch-specific template code
  - From: Paolo Carlini

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]