Re: Adoption of C subset standards

2017-01-09 Thread Richard Kenner
> It looks like MISRA should adjust its rules if it wants to support > open source. I can think of no reason why MISRA would want to do that given their goals. Can you?

Re: Adoption of C subset standards

2017-01-09 Thread Paul.Koning
> On Jan 9, 2017, at 4:08 PM, David Brown wrote: > ... > I found a reference to this in MISRA's forums: > > > > The post and reply are from 4 years ago, but I expect the situation is the > same now as then. Basically, MISRA are quite

Re: Adoption of C subset standards

2017-01-09 Thread David Brown
On 09/01/17 20:11, Richard Kenner wrote: I suppose that would be true if you refer to MISRA in the messages. If you don't then you're not using the trademark. The issue isn't the messages. but how you describe what you've done in, say, documentation or ChangeLog entries. If you claim, in any

Re: Adoption of C subset standards

2017-01-09 Thread David Brown
On 09/01/17 19:43, paul.kon...@dell.com wrote: On Jan 9, 2017, at 1:28 PM, Richard Kenner wrote: Regardless of that sort of issue, I think on previous occasions when the topic of MISRA (or other coding standard) checking came up, there has been a general opinion from the gcc developers tha

Re: Adoption of C subset standards

2017-01-09 Thread Richard Kenner
> I suppose that would be true if you refer to MISRA in the messages. > If you don't then you're not using the trademark. The issue isn't the messages. but how you describe what you've done in, say, documentation or ChangeLog entries. If you claim, in any way, that you're checking for "MISRA comp

Re: Adoption of C subset standards

2017-01-09 Thread Paul.Koning
> On Jan 9, 2017, at 1:55 PM, Richard Kenner wrote: > >> But as for a license, it's hard to see why that might be. You can't >> copyright rules (only a particular expression of same, and only to >> the extend that the "sweat of the brow" rule doesn't apply). And it >> doesn't sound like patent

Re: LTO remapping/deduction of machine modes of types/decls

2017-01-09 Thread Alexander Monakov
On Wed, 4 Jan 2017, Richard Biener wrote: > My suggestion at that time isn't likely working in practice due to the > limitations Jakub outlines below. The situation is a bit unfortunate > but expect to run into more host(!) dependences in the LTO bytecode. > Yes, while it would be nice to LTO x86_

Re: Adoption of C subset standards

2017-01-09 Thread Richard Kenner
> But as for a license, it's hard to see why that might be. You can't > copyright rules (only a particular expression of same, and only to > the extend that the "sweat of the brow" rule doesn't apply). And it > doesn't sound like patentable matter either. That said, if some > outfit thinks it ca

Re: Adoption of C subset standards

2017-01-09 Thread Paul.Koning
> On Jan 9, 2017, at 1:28 PM, Richard Kenner wrote: > >> Regardless of that sort of issue, I think on previous occasions when the >> topic of MISRA (or other coding standard) checking came up, there has >> been a general opinion from the gcc developers that the compiler itself >> is not the best

Re: input address reload issue

2017-01-09 Thread Jeff Law
On 01/09/2017 07:02 AM, Aurelien Buhrig wrote: On 06/01/2017 17:06, Jeff Law wrote: On 01/06/2017 03:20 AM, Aurelien Buhrig wrote: So the insn: (set (reg:QI 0 r0) (mem:QI (plus:SI (reg:SI 2 r2)(const_int 1)) is transformed into: (set (reg:SI 8 a0) (reg:SI 2 r2)) (set (reg:SI 8 a0) (const_int

Re: Adoption of C subset standards

2017-01-09 Thread Richard Kenner
> Regardless of that sort of issue, I think on previous occasions when the > topic of MISRA (or other coding standard) checking came up, there has > been a general opinion from the gcc developers that the compiler itself > is not the best place for this sort of checking - they recommend an > extern

Re: Adoption of C subset standards

2017-01-09 Thread David Brown
On 09/01/17 15:15, Nathan Sidwell wrote: > On 01/09/2017 08:58 AM, David Brown wrote: > >> I don't know about CERT-C, but one of the challenges of implementing >> MISRA coding standards checking in gcc is that the MISRA documents are >> not free. They are cheap (about $10, I think), but since the

Re: Adoption of C subset standards

2017-01-09 Thread Jonathan Wakely
On 9 January 2017 at 14:15, Nathan Sidwell wrote: > On 01/09/2017 08:58 AM, David Brown wrote: > >> I don't know about CERT-C, but one of the challenges of implementing >> MISRA coding standards checking in gcc is that the MISRA documents are >> not free. They are cheap (about $10, I think), but s

Re: Adoption of C subset standards

2017-01-09 Thread Jonathan Wakely
On 9 January 2017 at 14:22, Jonathan Wakely wrote: > On 9 January 2017 at 14:15, Nathan Sidwell wrote: >> On 01/09/2017 08:58 AM, David Brown wrote: >> >>> I don't know about CERT-C, but one of the challenges of implementing >>> MISRA coding standards checking in gcc is that the MISRA documents are

Re: Question about inlining and strict_aliasing

2017-01-09 Thread Martin Liška
On 01/09/2017 02:34 PM, Jan Hubicka wrote: >> Hello. >> >> I've been working on a patch that would cope with target and optimization >> (read PerFunction) >> in a proper way. I came to following test-case (slightly modified >> ./gcc/testsuite/gcc.c-torture/execute/alias-1.c): >> >> int val; >> >>

Re: Adoption of C subset standards

2017-01-09 Thread Nathan Sidwell
On 01/09/2017 08:58 AM, David Brown wrote: I don't know about CERT-C, but one of the challenges of implementing MISRA coding standards checking in gcc is that the MISRA documents are not free. They are cheap (about $10, I think), but since they are not free there are likely to be copyright comp

Re: input address reload issue

2017-01-09 Thread Aurelien Buhrig
On 06/01/2017 17:06, Jeff Law wrote: > On 01/06/2017 03:20 AM, Aurelien Buhrig wrote: >> So the insn: (set (reg:QI 0 r0) (mem:QI (plus:SI (reg:SI 2 r2)(const_int 1)) is transformed into: (set (reg:SI 8 a0) (reg:SI 2 r2)) (set (reg:SI 8 a0) (const_int 1)) (set (reg

Re: Adoption of C subset standards

2017-01-09 Thread David Brown
On 09/01/17 12:34, Jim MacArthur wrote: > Hi all, I've become involved in a group which seeks to refine previous > efforts in both safety-critical and secure coding standards (for example > MISRA and CERT-C). We note that in the past MISRA has been declined for > explicit inclusion in GCC but that

Re: Question about inlining and strict_aliasing

2017-01-09 Thread Jan Hubicka
> Hello. > > I've been working on a patch that would cope with target and optimization > (read PerFunction) > in a proper way. I came to following test-case (slightly modified > ./gcc/testsuite/gcc.c-torture/execute/alias-1.c): > > int val; > > int *ptr = &val; > float *ptr2 = &val; > > stati

Question about inlining and strict_aliasing

2017-01-09 Thread Martin Liška
Hello. I've been working on a patch that would cope with target and optimization (read PerFunction) in a proper way. I came to following test-case (slightly modified ./gcc/testsuite/gcc.c-torture/execute/alias-1.c): int val; int *ptr = &val; float *ptr2 = &val; static __attribute__((always_in

GCC 7.0.0 Status Report (2017-01-09), Stage 4 to start soon

2017-01-09 Thread Jakub Jelinek
The trunk is still in Stage 3 now, which means it is open for general bugfixing, but will enter Stage 4 on Thursday, 19th, end of day (timezone of your preference). Once that happens, only wrong-code fixes, regression bugfixes and documentation fixes will be allowed, as is normal for our release b

Adoption of C subset standards

2017-01-09 Thread Jim MacArthur
Hi all, I've become involved in a group which seeks to refine previous efforts in both safety-critical and secure coding standards (for example MISRA and CERT-C). We note that in the past MISRA has been declined for explicit inclusion in GCC but that parts of it and CERT-C are tested by individ

Re: Successful bootstrap and install of gcc (GCC) 6.3.0 on mips64el-unknown-linux-gnu

2017-01-09 Thread Dennis Luehring
are you only building gcc or also glibc/binutils? and building a kernel with minimal hello world init or something for testing? what about a dec-alpha build test :) Am 08.01.2017 um 21:27 schrieb Aaro Koskinen: Hi, Here's a report of a successful build and install of GCC: $ gcc-6.3.0/config.