On 09/19/16 23:27, Jeff Law wrote:
> On 09/19/2016 03:08 PM, Bernd Edlinger wrote:
>>>
>>> Would it work to break this up into distinct tests, exit()-ing from each
>>> function rather than returning back to main?
>>>
>>
>> Yes. I think how this test is designed, each function must be inlined,
>>
On 09/19/2016 03:08 PM, Bernd Edlinger wrote:
Would it work to break this up into distinct tests, exit()-ing from each
function rather than returning back to main?
Yes. I think how this test is designed, each function must be inlined,
or it will fail anyway. It was for instance impossible
On 09/19/16 22:19, Jeff Law wrote:
> On 09/15/2016 04:29 AM, Tom de Vries wrote:
>> On 31/08/16 07:42, Tom de Vries wrote:
>>> On 30/08/16 11:38, Bernd Edlinger wrote:
On 08/30/16 10:21, Tom de Vries wrote:
> On 29/08/16 18:43, Bernd Edlinger wrote:
>> Thanks!
>>
>> Actually
On 09/15/2016 04:29 AM, Tom de Vries wrote:
On 31/08/16 07:42, Tom de Vries wrote:
On 30/08/16 11:38, Bernd Edlinger wrote:
On 08/30/16 10:21, Tom de Vries wrote:
On 29/08/16 18:43, Bernd Edlinger wrote:
Thanks!
Actually my patch missed to fix one combination: -m32 with -fpic
make
On 31/08/16 07:42, Tom de Vries wrote:
On 30/08/16 11:38, Bernd Edlinger wrote:
On 08/30/16 10:21, Tom de Vries wrote:
On 29/08/16 18:43, Bernd Edlinger wrote:
Thanks!
Actually my patch missed to fix one combination: -m32 with -fpic
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c
On 30/08/16 11:38, Bernd Edlinger wrote:
On 08/30/16 10:21, Tom de Vries wrote:
On 29/08/16 18:43, Bernd Edlinger wrote:
Thanks!
Actually my patch missed to fix one combination: -m32 with -fpic
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c --tool_opts
'-m32 -fpic'"
FAIL:
On 08/30/16 10:21, Tom de Vries wrote:
> On 29/08/16 18:43, Bernd Edlinger wrote:
>> Thanks!
>>
>> Actually my patch missed to fix one combination: -m32 with -fpic
>>
>> make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c --tool_opts
>> '-m32 -fpic'"
>>
>> FAIL:
On 29/08/16 18:43, Bernd Edlinger wrote:
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c --tool_opts
'-m32 -fpic'"
FAIL: c-c++-common/ubsan/object-size-9.c -O2 execution test
FAIL: c-c++-common/ubsan/object-size-9.c -O2 -flto
-fno-use-linker-plugin -flto-partition=none
On 29/08/16 18:43, Bernd Edlinger wrote:
Thanks!
Actually my patch missed to fix one combination: -m32 with -fpic
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c --tool_opts
'-m32 -fpic'"
FAIL: c-c++-common/ubsan/object-size-9.c -O2 execution test
FAIL:
Thanks!
Actually my patch missed to fix one combination: -m32 with -fpic
make check-gcc-c++ RUNTESTFLAGS="ubsan.exp=object-size-9.c --tool_opts
'-m32 -fpic'"
FAIL: c-c++-common/ubsan/object-size-9.c -O2 execution test
FAIL: c-c++-common/ubsan/object-size-9.c -O2 -flto
On 17/09/15 20:08, Marek Polacek wrote:
On Thu, Sep 17, 2015 at 08:06:48PM +0200, Bernd Edlinger wrote:
Hi,
On Thu, 17 Sep 2015 10:39:04, Jeff Law wrote:
On 09/17/2015 09:00 AM, Marek Polacek wrote:
On Wed, Sep 09, 2015 at 07:48:15PM +0200, Bernd Edlinger wrote:
Hi,
On Wed, 9 Sep 2015
On 09/17/2015 09:00 AM, Marek Polacek wrote:
On Wed, Sep 09, 2015 at 07:48:15PM +0200, Bernd Edlinger wrote:
Hi,
On Wed, 9 Sep 2015 09:31:33, Jeff Law wrote:
You could probably make the function static or change its visibility via
a function attribute (there's a visibility attribute which can
On Wed, Sep 09, 2015 at 07:48:15PM +0200, Bernd Edlinger wrote:
> Hi,
>
> On Wed, 9 Sep 2015 09:31:33, Jeff Law wrote:
> > You could probably make the function static or change its visibility via
> > a function attribute (there's a visibility attribute which can take the
> > values default,
Hi,
On Thu, 17 Sep 2015 10:39:04, Jeff Law wrote:
>
> On 09/17/2015 09:00 AM, Marek Polacek wrote:
>> On Wed, Sep 09, 2015 at 07:48:15PM +0200, Bernd Edlinger wrote:
>>> Hi,
>>>
>>> On Wed, 9 Sep 2015 09:31:33, Jeff Law wrote:
You could probably make the function static or change its
On Thu, Sep 17, 2015 at 08:06:48PM +0200, Bernd Edlinger wrote:
> Hi,
>
> On Thu, 17 Sep 2015 10:39:04, Jeff Law wrote:
> >
> > On 09/17/2015 09:00 AM, Marek Polacek wrote:
> >> On Wed, Sep 09, 2015 at 07:48:15PM +0200, Bernd Edlinger wrote:
> >>> Hi,
> >>>
> >>> On Wed, 9 Sep 2015 09:31:33, Jeff
Hi Jeff,
On Tue, 8 Sep 2015 13:27:12, Jeff Law wrote:
>
> On 09/07/2015 07:46 AM, Bernd Edlinger wrote:
>> Hi,
>>
>> On Mon, 7 Sep 2015 12:07:00, Marek Polacek wrote:
>>>
>>> On Sun, Sep 06, 2015 at 07:21:13PM +0200, Bernd Edlinger wrote:
Hi,
we observed sporadic failures of the
On 09/09/2015 03:10 AM, Bernd Edlinger wrote:
Hi Jeff,
On Tue, 8 Sep 2015 13:27:12, Jeff Law wrote:
On 09/07/2015 07:46 AM, Bernd Edlinger wrote:
Hi,
On Mon, 7 Sep 2015 12:07:00, Marek Polacek wrote:
On Sun, Sep 06, 2015 at 07:21:13PM +0200, Bernd Edlinger wrote:
Hi,
we observed
Hi,
On Wed, 9 Sep 2015 09:31:33, Jeff Law wrote:
> You could probably make the function static or change its visibility via
> a function attribute (there's a visibility attribute which can take the
> values default, hidden protected or internal). Default visibility
> essentially means the
On 09/07/2015 07:46 AM, Bernd Edlinger wrote:
Hi,
On Mon, 7 Sep 2015 12:07:00, Marek Polacek wrote:
On Sun, Sep 06, 2015 at 07:21:13PM +0200, Bernd Edlinger wrote:
Hi,
we observed sporadic failures of the following two test cases (see PR64078):
c-c++-common/ubsan/object-size-9.c and
On Sun, Sep 06, 2015 at 07:21:13PM +0200, Bernd Edlinger wrote:
> Hi,
>
> we observed sporadic failures of the following two test cases (see PR64078):
> c-c++-common/ubsan/object-size-9.c and c-c++-common/ubsan/object-size-10.c
>
> For object-size-9.c this happens in a reproducible way when
Hi,
On Mon, 7 Sep 2015 12:07:00, Marek Polacek wrote:
>
> On Sun, Sep 06, 2015 at 07:21:13PM +0200, Bernd Edlinger wrote:
>> Hi,
>>
>> we observed sporadic failures of the following two test cases (see PR64078):
>> c-c++-common/ubsan/object-size-9.c and c-c++-common/ubsan/object-size-10.c
>>
>>
21 matches
Mail list logo
