Re: Alternative C compilers on x86_64 Linux?

alexfrunews@gmail.com
Mon, 5 Sep 2016 17:26:20 -0700 (PDT)

          From comp.compilers
Related articles
Alternative C compilers on x86_64 Linux? arnold@skeeve.com (2016-09-02)
Re: Alternative C compilers on x86_64 Linux? jacob@jacob.remcomp.fr (jacobnavia) (2016-09-05)
Re: Alternative C compilers on x86_64 Linux? nemo@invalid.invalid (Nemo) (2016-09-04)
Re: Alternative C compilers on x86_64 Linux? 221-501-9011@kylheku.com (Kaz Kylheku) (2016-09-04)
Re: Alternative C compilers on x86_64 Linux? bc@freeuk.com (BartC) (2016-09-05)
Re: Alternative C compilers on x86_64 Linux? fw@deneb.enyo.de (Florian Weimer) (2016-09-05)
Re: Alternative C compilers on x86_64 Linux? alexfrunews@gmail.com (2016-09-05)
Re: Alternative C compilers on x86_64 Linux? alexfrunews@gmail.com (2016-09-05)
Re: Alternative C compilers on x86_64 Linux? 221-501-9011@kylheku.com (Kaz Kylheku) (2016-09-06)
Re: Alternative C compilers on x86_64 Linux? 221-501-9011@kylheku.com (Kaz Kylheku) (2016-09-06)
Re: Alternative C compilers on x86_64 Linux? bc@freeuk.com (BartC) (2016-09-06)
Re: Alternative C compilers on x86_64 Linux? rockbrentwood@gmail.com (2016-09-07)
Re: diagnosing C errors, was Alternative C compilers on x86_64 Linux? bc@freeuk.com (BartC) (2016-09-09)
Re: diagnosing C errors, was Alternative C compilers on x86_64 Linux? 221-501-9011@kylheku.com (Kaz Kylheku) (2016-09-09)
[22 later articles]
| List of all articles for this month |
From: alexfrunews@gmail.com
Newsgroups: comp.compilers
Date: Mon, 5 Sep 2016 17:26:20 -0700 (PDT)
Organization: Compilers Central
References: 16-09-001 16-09-002
Injection-Info: miucha.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="67691"; mail-complaints-to="abuse@iecc.com"
Keywords: C
Posted-Date: 05 Sep 2016 22:51:09 EDT

On Sunday, September 4, 2016 at 3:56:56 PM UTC-7, jacobnavia wrote:
> Why should they care? If you write duplicate switch cases its not their
> fault, its yours.


It is a constraint violation, and a trivial one, that the compiler
must identify and report instead of silently producing code that is
broken or appears to work by chance.


Alex

Post a followup to this message

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