On Thu, Oct 03, 2019 at 12:16:46PM +0100, Maciej W. Rozycki wrote:
> On Thu, 3 Oct 2019, Segher Boessenkool wrote:
> > When a (conditional) branch executes, it is detected if the branch was
> > mispredicted, and if so it (and everything after it) is flushed. This is
> > similar to how it was done
On Thu, 3 Oct 2019, Segher Boessenkool wrote:
> > I don't think this is right. As I have just mentioned in a related
> > discussion elsewhere, the NVAX and NVAX+ implementations include a branch
> > predictor in their microarchitecture[1], so obviously they do execute
> > speculatively. I th
On Thu, Oct 03, 2019 at 03:12:34AM +0100, Maciej W. Rozycki wrote:
> On Fri, 20 Sep 2019, Jeff Law wrote:
>
> > > According to Bob Supnik (who is a very authoritative source on VAX),
> > >
> > >> Funny you should ask. The short answer is no. No VAX ever did
> > >> speculative or out of order exec
On 10/2/19 8:12 PM, Maciej W. Rozycki wrote:
> On Fri, 20 Sep 2019, Jeff Law wrote:
>
>>> According to Bob Supnik (who is a very authoritative source on VAX),
>>>
Funny you should ask. The short answer is no. No VAX ever did
speculative or out of order execution.
>>>
>>> As such, marking
On Fri, 20 Sep 2019, Jeff Law wrote:
> > According to Bob Supnik (who is a very authoritative source on VAX),
> >
> >> Funny you should ask. The short answer is no. No VAX ever did
> >> speculative or out of order execution.
> >
> > As such, marking VAX as not needing speculation barriers.
> >
On 9/17/19 2:59 PM, co...@sdf.org wrote:
> According to Bob Supnik (who is a very authoritative source on VAX),
>
>> Funny you should ask. The short answer is no. No VAX ever did
>> speculative or out of order execution.
>
> As such, marking VAX as not needing speculation barriers.
>
>
>
According to Bob Supnik (who is a very authoritative source on VAX),
> Funny you should ask. The short answer is no. No VAX ever did
> speculative or out of order execution.
As such, marking VAX as not needing speculation barriers.
PR target/86811
* config/vax/vax.c (TARGET_HAVE
