> On Feb 13, 2018, at 5:28 PM, Will Schmidt wrote:
>
> On Thu, 2018-02-08 at 17:48 -0600, Segher Boessenkool wrote:
>> Hi!
>>
>> On Wed, Feb 07, 2018 at 09:14:59AM -0600, Will Schmidt wrote:
>>> Our VEC_SLD definitions were mistakenly allowing the third argument to be
>>> of an invalid type, t
On Thu, 2018-02-08 at 17:48 -0600, Segher Boessenkool wrote:
> Hi!
>
> On Wed, Feb 07, 2018 at 09:14:59AM -0600, Will Schmidt wrote:
> > Our VEC_SLD definitions were mistakenly allowing the third argument to be
> > of an invalid type, triggering an ICE (on invalid code) later in the build
> > pr
On Thu, 2018-02-08 at 17:48 -0600, Segher Boessenkool wrote:
> Hi!
>
> On Wed, Feb 07, 2018 at 09:14:59AM -0600, Will Schmidt wrote:
> > Our VEC_SLD definitions were mistakenly allowing the third argument to be
> > of an invalid type, triggering an ICE (on invalid code) later in the build
> > pr
Hi!
On Wed, Feb 07, 2018 at 09:14:59AM -0600, Will Schmidt wrote:
> Our VEC_SLD definitions were mistakenly allowing the third argument to be
> of an invalid type, triggering an ICE (on invalid code) later in the build
> process. This fixes those definitions. The nearby VEC_SLDW definitions ha
Hi,
Our VEC_SLD definitions were mistakenly allowing the third argument to be
of an invalid type, triggering an ICE (on invalid code) later in the build
process. This fixes those definitions. The nearby VEC_SLDW definitions have
the same issue, those have been fixed as part of this patch too.
T
