On Thu, Jul 21, 2016 at 11:06:06AM +0800, Liang, Kan wrote:
Hi Fengguang,
I located the unreachable instruction which is ud2.
This instruction will raise invalid opcode exception. So I think
normally it should not be reached. Also ud2 should be generated by
compiler, not our codes.
It's grea
Snapshot gcc-4.9-20160720 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20160720/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.9 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
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
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
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
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
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
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.
>>
>>
On 07/20/2016 02:28 PM, Jakub Jelinek wrote:
On Wed, Jul 20, 2016 at 02:19:15PM -0600, Martin Sebor wrote:
Is there a way to express a requirement that a single line cause
two or more diagnostic messages (in any order) each matching one
of the regex strings?
Sure, and it is used many times in
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
On Wed, Jul 20, 2016 at 02:19:15PM -0600, Martin Sebor wrote:
> Is there a way to express a requirement that a single line cause
> two or more diagnostic messages (in any order) each matching one
> of the regex strings?
Sure, and it is used many times in the testsuite.
whatever; /* { dg-error "
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
When multiple diagnostics for a given line in a test are expected,
I have been using the vertical bar ('|') in regular expression
arguments to DejaGnu directives like dg-error and dg-warning on
the assumption that all are matched.
This use appears to be sanctioned by the GCC TestCaseWriting Wiki
On Tue, 2016-07-19 at 16:10 -0700, David Edelsohn wrote:
> Hi, David
>
> I don't believe that hardware easily is available. We probably could
> arrange for access, if it is necessary, but it is not accessible
> through the IBM Community Development system for Linux on z Systems
> because this isn
On Wed, Jul 20, 2016 at 1:46 PM, Prathamesh Kulkarni
wrote:
> On 20 July 2016 at 11:34, Richard Biener wrote:
>> On Tue, Jul 19, 2016 at 10:09 PM, Prasad Ghangal
>> wrote:
>>> On 19 July 2016 at 11:04, Richard Biener wrote:
On July 18, 2016 11:05:58 PM GMT+02:00, David Malcolm
wrote
On 20 July 2016 at 11:34, Richard Biener wrote:
> On Tue, Jul 19, 2016 at 10:09 PM, Prasad Ghangal
> wrote:
>> On 19 July 2016 at 11:04, Richard Biener wrote:
>>> On July 18, 2016 11:05:58 PM GMT+02:00, David Malcolm
>>> wrote:
On Tue, 2016-07-19 at 00:52 +0530, Prasad Ghangal wrote:
>
On Tue, Jul 19, 2016 at 10:09 PM, Prasad Ghangal
wrote:
> On 19 July 2016 at 11:04, Richard Biener wrote:
>> On July 18, 2016 11:05:58 PM GMT+02:00, David Malcolm
>> wrote:
>>>On Tue, 2016-07-19 at 00:52 +0530, Prasad Ghangal wrote:
On 19 July 2016 at 00:25, Richard Biener
wrote:
>>>
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
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
19 matches
Mail list logo
