public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Paulo Matos <pmatos@broadcom.com>,
	Andreas Schwab <schwab@linux-m68k.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Regression [v850,mep...]: sign_extend in loop breaks zero-overhead loop generation
Date: Thu, 30 Jan 2014 18:07:00 -0000	[thread overview]
Message-ID: <52EA74A8.4060303@redhat.com> (raw)
In-Reply-To: <19EB96622A777C4AB91610E763265F463F30B5@SJEXCHMB14.corp.ad.broadcom.com>

On 01/30/14 08:19, Paulo Matos wrote:
>> -----Original Message-----
>> From: Andreas Schwab [mailto:schwab@linux-m68k.org]
>> Sent: 30 January 2014 15:15
>> To: Paulo Matos
>> Cc: gcc@gcc.gnu.org
>> Subject: Re: Regression [v850,mep...]: sign_extend in loop breaks zero-overhead
>> loop generation
>>
>> Paulo Matos <pmatos@broadcom.com> writes:
>>
>>> If instead I write:
>>> void
>>> foo (short blockSize)
>>> {
>>>    short i;
>>>    unsigned short loopCount;
>>>    loopCount = (unsigned short) (blockSize + delayLength) % 8;
>>>    for (i = 0; i < loopCount; i++)
>>>        *temp_ptr++ = x ^ *temp_ptr;
>>> }
>>
>> This is still undefined.
>>
>
> OK, of course. Don't know what I am doing today.
> It's undefined because 'i' might overflow... I will get back to this. Thanks for pointing this out.
When you've got it sorted out, go ahead and file a BZ, include the 
regression markers so that it shows up in the searches most of us are 
paying the most attention to right now.

jeff

  reply	other threads:[~2014-01-30 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 14:05 Paulo Matos
2014-01-30 14:37 ` Andreas Schwab
2014-01-30 15:00   ` Paulo Matos
2014-01-30 15:19     ` Andreas Schwab
2014-01-30 17:29       ` Paulo Matos
2014-01-30 18:07         ` Jeff Law [this message]
2014-01-31 10:40           ` Paulo Matos

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52EA74A8.4060303@redhat.com \
    --to=law@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=pmatos@broadcom.com \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).