On 2018-11-29 09:13:04 [-0800], Dave Hansen wrote:
> On 11/29/18 6:17 AM, Sebastian Andrzej Siewior wrote:
> > This is broken since v4.12-rc1. This is known [1] since April this year.
> > Should I send a removal patch for MPX or is someone actually going to
> > fix this? Or do we wait for gcc-9 to
On 2018-11-29 09:13:04 [-0800], Dave Hansen wrote:
> On 11/29/18 6:17 AM, Sebastian Andrzej Siewior wrote:
> > This is broken since v4.12-rc1. This is known [1] since April this year.
> > Should I send a removal patch for MPX or is someone actually going to
> > fix this? Or do we wait for gcc-9 to
On 11/29/18 6:17 AM, Sebastian Andrzej Siewior wrote:
> This is broken since v4.12-rc1. This is known [1] since April this year.
> Should I send a removal patch for MPX or is someone actually going to
> fix this? Or do we wait for gcc-9 to be released?
I've got a git tree prepared to do MPX
On 11/29/18 6:17 AM, Sebastian Andrzej Siewior wrote:
> This is broken since v4.12-rc1. This is known [1] since April this year.
> Should I send a removal patch for MPX or is someone actually going to
> fix this? Or do we wait for gcc-9 to be released?
I've got a git tree prepared to do MPX
so I've been testing my FPU patches and noticed that the test
mpx-mini-test_32 [0] fails on 64bit host.
I went back to v4.4 and it didn't pass there fully, it ended with:
| starting mpx bounds table test
| ERROR: siginfo bounds do not match shadow bounds for register 0
But it did way more than it
so I've been testing my FPU patches and noticed that the test
mpx-mini-test_32 [0] fails on 64bit host.
I went back to v4.4 and it didn't pass there fully, it ended with:
| starting mpx bounds table test
| ERROR: siginfo bounds do not match shadow bounds for register 0
But it did way more than it
6 matches
Mail list logo
