public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "malitzke at metronets dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/32314] for gcc-4.2gcc-4disable-decimal-float not working on i686, powerpc, sparc. gcc-4.3.0 Date: Wed, 13 Jun 2007 07:09:00 -0000 [thread overview] Message-ID: <20070613070917.27148.qmail@sourceware.org> (raw) In-Reply-To: <bug-32314-11706@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from malitzke at metronets dot com 2007-06-13 07:09 ------- All I want for gcc is that it meets both the letter __and__ the spirit of applicable contracts and specifications. First, the GPL is a contract, do __not__ take my word for it but consult a lawyer. Second, the C standard can be and should be made part of a contract like a chip manufacturer would sign with a major purchaser like Ford or GM for embedded chips and the included support software like gcc. After working 80 hours with paid overtime) as a highly regarded real-time assembly programmer (before C became available) I tripled my income (no paid overtime) as an international telecommunications consultant (really RFP writer, contract negotiator, acceptance tester), project engineer, co-writer of ITU (International Telecommunications Union) specifications, and US-representative on technical supervisory committees. I caused significant economic harm to contractors (benefiting my employer or organizations I consulted for) by incorporating ITU standards in contracts. Therefore I have some knowledge of these matters. Three; gcc-4.3.0 and gcc-4.2.2 will most likely be released under the GPL3 (which not only is intended to replace GPL2 but also the lesser GPL for libraries) Four: under the C specification compiler writers can furnish extensions. But, these extensions are required to have disablers. Five: Yes, gcc is furnished by gnu.org mithout any warranty, or even being fit for merchantability. However, __hidden__ items like libgcc might constitute borderline cases. In the hands of a skillful lawyer, like Mr Edwards, these hidden items could cause a lot of grief to gnu.org and the maintainers as a group. Microsoft could even file an amicus curieae brief. -- malitzke at metronets dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32314
next prev parent reply other threads:[~2007-06-13 7:09 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-13 5:35 [Bug c/32314] New: " malitzke at metronets dot com 2007-06-13 5:44 ` [Bug c/32314] " pinskia at gcc dot gnu dot org 2007-06-13 5:46 ` pinskia at gcc dot gnu dot org 2007-06-13 5:48 ` malitzke at metronets dot com 2007-06-13 6:06 ` malitzke at metronets dot com 2007-06-13 6:26 ` pinskia at gcc dot gnu dot org 2007-06-13 7:09 ` malitzke at metronets dot com [this message] 2007-06-13 7:30 ` pinskia at gcc dot gnu dot org 2007-06-16 13:09 ` malitzke at metronets dot com 2007-06-17 6:54 ` pinskia at gcc dot gnu dot org 2007-06-17 18:02 ` malitzke at metronets dot com 2007-06-17 23:30 ` malitzke at metronets dot com 2007-06-17 23:34 ` pinskia at gcc dot gnu dot org 2007-06-18 0:06 ` malitzke at metronets dot com 2007-06-18 0:26 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070613070917.27148.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).