Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!1.eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Sequence points and commit to memory Date: Tue, 19 May 2015 08:37:21 -0700 Organization: None to speak of Lines: 26 Message-ID: <87wq0437f2.fsf@kst-u.example.com> References: <555A7049.6010405@verizon.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="9be37d943435275679235b07c7947eef"; logging-data="7595"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX186aKrB2l5Rjgfui4CI4enL" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:N46j8J6aaBRV2C5UKmJarmrqxPM= sha1:NamFldxz1Ap0vUSa3iNTr6gpqaQ= Xref: csiph.com comp.lang.c:62290 David Brown writes: [...] > C has no concept of interrupts, or of flow changes outside the sequence > given in the source code, or of actions or effects outside the source > code, except through the use of "volatile". C compilers "support" > interrupts in that they know there is no such thing! This applies to > /all/ C compilers on /all/ platforms - there are very few processors > that don't have some sort of interrupt mechanism. [...] N1570 5.2.3 is titled "Signals and interrupts". It requires that a function's behavior is not altered when a signal is received, as long as it uses only objects with automatic storage duration. 7.14 describes the header. 7.26 describes the header. The "Signals and interrupts" discussion and go back to C89/C90; is new in C11, and is optional. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"