Re: ubsan and Dejagnu not having a big enough buffer in some cases

On Wed, Jul 20, 2016 at 3:07 PM, Andrew Pinski wrote: > On Wed, Jul 20, 2016 at 2:57 PM, H.J. Lu wrote: >> On Wed, Jul 20, 2016 at 2:20 PM, Jeff Law wrote: >>> On 07/20/2016 03:09 PM, Andrew Pinski wrote: On Wed, Jul 20, 2016 at 2:02 PM, Andrew Pinski wrote: > > On Wed, Jul 20

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On Wed, Jul 20, 2016 at 2:57 PM, H.J. Lu wrote: > On Wed, Jul 20, 2016 at 2:20 PM, Jeff Law wrote: >> On 07/20/2016 03:09 PM, Andrew Pinski wrote: >>> >>> On Wed, Jul 20, 2016 at 2:02 PM, Andrew Pinski wrote: On Wed, Jul 20, 2016 at 1:32 PM, Jeff Law wrote: > > On 07/20/2016 0

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On Wed, Jul 20, 2016 at 2:20 PM, Jeff Law wrote: > On 07/20/2016 03:09 PM, Andrew Pinski wrote: >> >> On Wed, Jul 20, 2016 at 2:02 PM, Andrew Pinski wrote: >>> >>> On Wed, Jul 20, 2016 at 1:32 PM, Jeff Law wrote: On 07/20/2016 02:21 PM, Segher Boessenkool wrote: > > > On We

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On 07/20/2016 03:09 PM, Andrew Pinski wrote: On Wed, Jul 20, 2016 at 2:02 PM, Andrew Pinski wrote: On Wed, Jul 20, 2016 at 1:32 PM, Jeff Law wrote: On 07/20/2016 02:21 PM, Segher Boessenkool wrote: On Wed, Jul 20, 2016 at 12:48:09PM +0530, Senthil Kumar Selvaraj wrote: I see this for some

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On Wed, Jul 20, 2016 at 2:02 PM, Andrew Pinski wrote: > On Wed, Jul 20, 2016 at 1:32 PM, Jeff Law wrote: >> On 07/20/2016 02:21 PM, Segher Boessenkool wrote: >>> >>> On Wed, Jul 20, 2016 at 12:48:09PM +0530, Senthil Kumar Selvaraj wrote: > > I see this for some of the larger C frontend te

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On Wed, Jul 20, 2016 at 1:32 PM, Jeff Law wrote: > On 07/20/2016 02:21 PM, Segher Boessenkool wrote: >> >> On Wed, Jul 20, 2016 at 12:48:09PM +0530, Senthil Kumar Selvaraj wrote: I see this for some of the larger C frontend tests with lots of expected errors/warnings as well. >> >>

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On 07/20/2016 02:21 PM, Segher Boessenkool wrote: On Wed, Jul 20, 2016 at 12:48:09PM +0530, Senthil Kumar Selvaraj wrote: I see this for some of the larger C frontend tests with lots of expected errors/warnings as well. I also see this for tests with small output, but it happens more often fo

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On Wed, Jul 20, 2016 at 12:48:09PM +0530, Senthil Kumar Selvaraj wrote: > > I see this for some of the larger C frontend tests with lots of expected > > errors/warnings as well. I also see this for tests with small output, but it happens more often for tests with big output. > Are you guys getti

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On July 20, 2016 9:18:09 AM GMT+02:00, Senthil Kumar Selvaraj wrote: > >Richard Biener writes: > >> On July 20, 2016 2:01:18 AM GMT+02:00, Andrew Pinski > wrote: >>>Hi, >>> I noticed that ubsan testsuite sometimes has failures due to >dejagnu >>>buffer gets full and we no longer match on the out

Re: ubsan and Dejagnu not having a big enough buffer in some cases

Richard Biener writes: > On July 20, 2016 2:01:18 AM GMT+02:00, Andrew Pinski > wrote: >>Hi, >> I noticed that ubsan testsuite sometimes has failures due to dejagnu >>buffer gets full and we no longer match on the output any more. >>As you can see from the .log file: >>/data1/jenkins/workspace

Re: ubsan and Dejagnu not having a big enough buffer in some cases

On July 20, 2016 2:01:18 AM GMT+02:00, Andrew Pinski wrote: >Hi, > I noticed that ubsan testsuite sometimes has failures due to dejagnu >buffer gets full and we no longer match on the output any more. >As you can see from the .log file: >/data1/jenkins/workspace/BuildThunderX_native_gcc_6/gcc/gcc