Re: How to avoid code elimination

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: phi gcc <phi.gcc@xxxxxxxxx>, "gcc-help@xxxxxxxxxxx" <gcc-help@xxxxxxxxxxx>
Subject: Re: How to avoid code elimination
From: Andrew Haley <aph@xxxxxxxxxx>
Date: Sun, 26 Nov 2017 13:45:55 +0000
In-reply-to: <CADieKzs=0roe90qqqM4KWNdA5bQipJnY+eMPCL4j3jWthruAjg@mail.gmail.com>
References: <CADieKzuqPyfSbbnBaN8RDWc03MSznjXPa_-oD8qpGNkDwDQ4ew@mail.gmail.com> <CADieKzs=0roe90qqqM4KWNdA5bQipJnY+eMPCL4j3jWthruAjg@mail.gmail.com>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0

On 26/11/17 12:30, phi gcc wrote:
> asm("nop"); seems to be good enough at all -O level so its even better.

That's what I always do.

-- 
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

References:
- How to avoid code elimination
  - From: phi gcc
- Re: How to avoid code elimination
  - From: phi gcc

Prev by Date: Re: How to avoid code elimination
Next by Date: Re: Need help debugging likely g++ preprocessor bug
Previous by thread: Re: How to avoid code elimination
Next by thread: Re: How to avoid code elimination
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux