Re: volatile in struct member

From	raltbos@xs4all.nl (Richard Bos)
Newsgroups	comp.lang.c
Subject	Re: volatile in struct member
Date	2016-09-30 20:57 +0000
Organization	Go wash your mouth.
Message-ID	<57eed1b3.4378625@news.xs4all.nl> (permalink)
References	<dc811de3-cad5-4f57-b68d-dd8b0252e507@googlegroups.com> <nslpnq$u9r$1@dont-email.me> <a85b1a45-8301-4648-bbc1-6791506aed9c@googlegroups.com> <nsm59f$7a3$1@dont-email.me> <19553db9-a75b-4cc7-9f12-88a303302a51@googlegroups.com>

Show all headers | View raw

supercat@casperkitty.com wrote:

> On Friday, September 30, 2016 at 11:53:24 AM UTC-5, James Kuyper wrote:
> > Well, of course. The #pragma must be known by to the compiler that
> > performs the static analysis. Use the #pragma with any other compiler
> > and it's effectively just a different kind of comment.
> 
> The Standard imposes no requirements with regard to the behavior of any
> program which contains a #pragma directive whose meaning is not explicitly
> specified.  It would have been helpful to define "ownership" of certain
> pragma names, such that every compiler than encountered a line starting with
> e.g. "#pragma ACME" would be required to either process the line in the
> fashion defined by Acme Compiler Corporation or else ignore the line
> altogether, but the Standard is silent on such things.

Helpful, and entirely impossible.

Richard

Thread

volatile in struct member Thiago Adams <thiago.adams@gmail.com> - 2016-09-30 04:52 -0700
  Re: volatile in struct member Malcolm McLean <malcolm.mclean5@btinternet.com> - 2016-09-30 05:50 -0700
    Re: volatile in struct member Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-09-30 14:42 +0100
      Re: volatile in struct member Gareth Owen <gwowen@gmail.com> - 2016-09-30 22:09 +0100
        Re: volatile in struct member Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-09-30 22:24 +0100
  Re: volatile in struct member Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-09-30 14:29 +0100
    Re: volatile in struct member David Brown <david.brown@hesbynett.no> - 2016-09-30 16:22 +0200
      Re: volatile in struct member Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-09-30 15:51 +0100
        Re: volatile in struct member David Brown <david.brown@hesbynett.no> - 2016-09-30 17:07 +0200
    Re: volatile in struct member Tim Rentsch <txr@alumni.caltech.edu> - 2016-10-08 15:48 -0700
  Re: volatile in struct member David Brown <david.brown@hesbynett.no> - 2016-09-30 15:36 +0200
    Re: volatile in struct member Thiago Adams <thiago.adams@gmail.com> - 2016-09-30 06:47 -0700
      Re: volatile in struct member James Kuyper <jameskuyper@verizon.net> - 2016-09-30 12:53 -0400
        Re: volatile in struct member supercat@casperkitty.com - 2016-09-30 10:18 -0700
          Re: volatile in struct member raltbos@xs4all.nl (Richard Bos) - 2016-09-30 20:57 +0000
            Re: volatile in struct member supercat@casperkitty.com - 2016-09-30 14:46 -0700
        Re: volatile in struct member Thiago Adams <thiago.adams@gmail.com> - 2016-09-30 10:22 -0700
          Re: volatile in struct member jameskuyper@verizon.net - 2016-09-30 14:08 -0700

csiph-web