Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.c > #160217

Re: Infinite recursion detection criteria (correct C code)

Path csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups comp.lang.c
Subject Re: Infinite recursion detection criteria (correct C code)
Date Mon, 19 Apr 2021 04:01:09 -0700
Organization A noiseless patient Spider
Lines 20
Message-ID <86pmyqh72i.fsf@linuxsc.com> (permalink)
References <0e298c6f-071f-45d2-b744-f8a47e67a546n@googlegroups.com> <ME%dI.3794$8O4.1675@fx16.iad> <mo6dndXeg4wLCOX9nZ2dnUU7-cXNnZ2d@giganews.com> <J11eI.3991$v3H9.3879@fx01.iad> <sZGdnTBe37YIPOX9nZ2dnUU7-VfNnZ2d@giganews.com> <-62dnYOeXOSoN-X9nZ2dnUU7-aHNnZ2d@giganews.com> <s5d6dn$hdi$1@dont-email.me> <TKKdnYUfUOq1tef9nZ2dnUU7-NnNnZ2d@giganews.com> <YwqeI.48976$ST2.30987@fx47.iad> <s5dqmg$hkg$1@gioia.aioe.org> <s5drqq$soe$1@gioia.aioe.org> <4f639830-6a91-4c4f-8fa3-2e0cc85c7170n@googlegroups.com> <87sg3par0e.fsf@bsb.me.uk> <5cf2d72e-a725-48fb-a340-3423501fce0cn@googlegroups.com> <Ua6dnXWIW-ybs-b9nZ2dnUU7-WvNnZ2d@giganews.com> <xYUeI.8111$v3H9.971@fx01.iad> <vtKdnQb2zr-d1uH9nZ2dnUU78Q2dnZ2d@giganews.com> <fb0f032d-2e36-45fa-b95e-7b41e82db4d2n@googlegroups.com> <k9mdnakMZo6f9-H9nZ2dnUU7-T3NnZ2d@giganews.com> <20210418152814.400@kylheku.com> <s5ihs4$fgp$1@dont-email.me>
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
Injection-Info reader02.eternal-september.org; posting-host="06b334b85b44a22c3ab1a4f53205352f"; logging-data="5792"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+f+Z/W+plS08BWwDRPNLl27JIC5RBuly0="
User-Agent Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock sha1:skq8K6mjY8XTiZ897SFTWr/flVc= sha1:8l9//jTQEh5vkTMw0FIxPBviST0=
Xref csiph.com comp.lang.c:160217

Show key headers only | View raw


Jeff Barnett <jbb@notatt.com> writes:

[...]

> What about the following thoughts:
>
> 1) The architecture of the execution engine provides for traps
> (interrupts) to be signaled in cases of arithmetic errors such as
> divide by zero, under/over flow, etc.  Thus, almost every arithmetic
> instruction is an instance of "conditional" execution.  Also
> consider timer and external signal interrupts and it becomes quite
> clear that conditions 1 thru 4 above need context in order to
> validate any inferences from them.
>
> Interesting question given the use of a simulator:  How much is
> really simulated?

Since neither the thoughts nor the discussion preceding them has
anything to do with the C programming language, they should be
posted somewhere else, and not in comp.lang.c.

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Infinite recursion detection criteria (correct C code) olcott <NoOne@NoWhere.com> - 2021-04-18 12:19 -0500
  Re: Infinite recursion detection criteria (correct C code) Kaz Kylheku <563-365-8930@kylheku.com> - 2021-04-18 22:57 +0000
    Re: Infinite recursion detection criteria (correct C code) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-04-18 16:14 -0700
      Re: Infinite recursion detection criteria (correct C code) Kaz Kylheku <563-365-8930@kylheku.com> - 2021-04-19 17:01 +0000
        Re: Infinite recursion detection criteria (correct C code) Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-04-19 13:13 -0700
    Re: Infinite recursion detection criteria (correct C code) olcott <NoOne@NoWhere.com> - 2021-04-18 18:23 -0500
    Re: Infinite recursion detection criteria (correct C code) Jeff Barnett <jbb@notatt.com> - 2021-04-18 18:11 -0600
      Re: Infinite recursion detection criteria (correct C code) olcott <NoOne@NoWhere.com> - 2021-04-18 19:25 -0500
        Re: Infinite recursion detection criteria (correct C code) "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2021-04-18 18:04 -0700
      Re: Infinite recursion detection criteria (correct C code) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-04-19 04:01 -0700
    Re: Infinite recursion detection criteria (agreement check) olcott <NoOne@NoWhere.com> - 2021-04-18 20:13 -0500
      Re: Infinite recursion detection criteria (agreement check) olcott <NoOne@NoWhere.com> - 2021-04-18 20:16 -0500
      Re: Infinite recursion detection criteria (agreement check) Kaz Kylheku <563-365-8930@kylheku.com> - 2021-04-19 16:59 +0000
        Re: Infinite recursion detection criteria (agreement check) olcott <NoOne@NoWhere.com> - 2021-04-19 12:27 -0500
          Re: Infinite recursion detection criteria (agreement check) Kaz Kylheku <563-365-8930@kylheku.com> - 2021-04-19 17:40 +0000
    Re: Infinite recursion detection criteria (correct C code) Tim Rentsch <tr.17687@z991.linuxsc.com> - 2021-04-19 04:06 -0700
  Re: Infinite recursion detection criteria (correct C code) olcott <NoOne@NoWhere.com> - 2021-04-18 21:16 -0500
    Re: Infinite recursion detection criteria (correct C code) Richard Damon <Richard@Damon-Family.org> - 2021-04-18 22:26 -0400
      Re: Infinite recursion detection criteria (correct C code) olcott <NoOne@NoWhere.com> - 2021-04-18 21:29 -0500
      Re: Infinite recursion detection criteria (correct C code) olcott <NoOne@NoWhere.com> - 2021-04-19 10:40 -0500

csiph-web