Re: how to avoid a memset() optimization

"Joachim Durchholz" <joachim_d@gmx.de>
17 Nov 2002 22:56:55 -0500

          From comp.compilers
Related articles
[8 earlier articles]
Re: how to avoid a memset() optimization dobes@dobesland.com (Dobes Vandermeer) (2002-11-13)
Re: how to avoid a memset() optimization fjh@cs.mu.OZ.AU (Fergus Henderson) (2002-11-13)
Re: how to avoid a memset() optimization jvorbrueggen@mediasec.de (Jan C. =?iso-8859-1?Q?Vorbr=FCggen?=) (2002-11-13)
Re: how to avoid a memset() optimization usenet-1ugeabe@qeng-ho.org (Arthur Chance) (2002-11-13)
Re: how to avoid a memset() optimization cfc@shell01.TheWorld.com (Chris F Clark) (2002-11-15)
Re: how to avoid a memset() optimization usenet-1ugeabe@qeng-ho.org (Arthur Chance) (2002-11-15)
Re: how to avoid a memset() optimization joachim_d@gmx.de (Joachim Durchholz) (2002-11-17)
Re: how to avoid a memset() optimization cfc@shell01.TheWorld.com (Chris F Clark) (2002-11-20)
Re: how to avoid a memset() optimization thp@cs.ucr.edu (2002-11-24)
Re: how to avoid a memset() optimization n1096001003.ch@chch.demon.co.uk (Charles Bryant) (2002-12-01)
| List of all articles for this month |
From: "Joachim Durchholz" <joachim_d@gmx.de>
Newsgroups: comp.compilers
Date: 17 Nov 2002 22:56:55 -0500
Organization: Compilers Central
References: 02-11-030 02-11-069 02-11-084
Keywords: C, code, comment
Posted-Date: 17 Nov 2002 22:56:55 EST

Chris F Clark wrote:
>
> The MIPS compiler suite had exactly this behavior. [...]
>
  > Later the DEC group I consulted for(*), took this apporach
  > even further, and wrote "OM" (object modifier) which took
  > executable images (of machine language instructions) and
  > optimized them.


Did these tools honor "volatile" modifiers? I'd assume that for the MIPS
compiler suite, but it's hard to imagine that for an OM-style optimizer.


Regards,
Joachim
[Same question for the other sequence point stuff. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.