develooper Front page | perl.perl5.porters | Postings from July 2010

Re: [perl #76438] peephole optimiser could prune more dead code

Thread Previous | Thread Next
From:
David Golden
Date:
July 12, 2010 04:07
Subject:
Re: [perl #76438] peephole optimiser could prune more dead code
Message ID:
AANLkTimlGCccEMZtMyvwsF69liwhhkhl0Nh4mYUWWmlQ@mail.gmail.com
On Mon, Jul 12, 2010 at 12:51 AM, Eric Brine <ikegami@adaelis.com> wrote:
> On Sun, Jul 11, 2010 at 10:22 PM, David Golden <xdaveg@gmail.com> wrote:
>>
>> I'm suggesting that we disclaim any implicit guarantee that the
>> compiler won't optimize away expressions that have side effects when
>> evaluated.
>
> Without that guarantee,
>
> my $x = f()
>    or DEBUG && warn(...);
> return $x;
>
> would be buggy. Dunno if that matters

I said "... have side effects when evaluated ..." but your example has
a side effect (functional call) in an assignment before the logic
expression.  Maybe "evaluated" isn't the right term, but I was
intending it to mean the action of reading a value from a variable.

David

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About