From: Andi Hellmund <mail@andihellmund.com>
To: Drasko DRASKOVIC <drasko.draskovic@gmail.com>
Cc: kevin diggs <diggskevin38@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: need volatile for asm?
Date: Wed, 16 Feb 2011 11:18:00 -0000 [thread overview]
Message-ID: <4D5BAE09.7060808@andihellmund.com> (raw)
In-Reply-To: <AANLkTi=bBcrTy8Ab7ZUu=mn27mYfqs1y6cK74nMPw4yX@mail.gmail.com>
> Would this be portable check, guaranteeing that compilation on other
> machine with other gcc version will not do opposite ?
You are right, this is definitely NOT portable
> And anyway, why not always putting it to volatile ? Once you started
> embedding asm code, I guess you had a good reason for it to appear in
> the output code...
Good point.
Andi
next prev parent reply other threads:[~2011-02-16 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 23:58 kevin diggs
2011-02-16 5:25 ` Andi Hellmund
2011-02-16 10:33 ` Andrew Haley
2011-02-16 10:59 ` Drasko DRASKOVIC
2011-02-16 11:18 ` Andi Hellmund [this message]
2011-02-16 12:12 ` David Brown
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=4D5BAE09.7060808@andihellmund.com \
--to=mail@andihellmund.com \
--cc=diggskevin38@gmail.com \
--cc=drasko.draskovic@gmail.com \
--cc=gcc-help@gcc.gnu.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).