Re: const volatile behaviour change in GCC 7

> On Sep 22, 2016, at 6:17 AM, David Brown wrote: > > ... > Your trouble is that your two pointers, cur and end, are pointing at > different variables. Comparing two pointers that are independent (i.e., > not pointing to parts of the same aggregate object) is undefined - the > compiler can assu

Re: const volatile behaviour change in GCC 7

> On Sep 22, 2016, at 11:16 AM, David Brown wrote: > > On 22/09/16 16:57, paul.kon...@dell.com wrote: >> >>> On Sep 22, 2016, at 6:17 AM, David Brown wrote: >>> >>> ... >>> Your trouble is that your two pointers, cur and end, are pointing at >>> different variables. Comparing two pointers th

Re: const volatile behaviour change in GCC 7

> On Sep 22, 2016, at 11:31 AM, Richard Earnshaw (lists) > wrote: > >>> ... >>> void rtems_initialize_executive(void) >>> { >>> uintptr_t cur = (uintptr_t) _Linker_set__Sysinit_begin; >>> uintptr_t end = (uintptr_t) _Linker_set__Sysinit_end; >> >> I would not expect the compiler to apply point

Re: Converting to LRA (calling all maintainers)

> On Sep 25, 2016, at 4:46 AM, Eric Botcazou wrote: > >> There is no hurry to kill old reload. As you say, many targets will >> not be converted soon. But one day it will be removed. Not in GCC 7, >> not in GCC 8 almost certainly. But one day. > > Certainly not in GCC 8, the top priority is

Re: style convention: /*foo_p=*/ to annotate bool arguments

> On Oct 3, 2016, at 7:48 PM, Martin Sebor wrote: > > In a recent review Jason and I discussed the style convention > commonly followed in the C++ front end to annotate arguments > in calls to functions taking bool parameters with a comment > along the lines of > > foo (1, 2, /*bar_p=*/true);

Re: style convention: /*foo_p=*/ to annotate bool arguments

> On Oct 4, 2016, at 11:46 AM, Jonathan Wakely wrote: > > On 4 October 2016 at 16:41, wrote: >> >>> On Oct 3, 2016, at 7:48 PM, Martin Sebor wrote: >>> >>> In a recent review Jason and I discussed the style convention >>> commonly followed in the C++ front end to annotate arguments >>> in c

Re: style convention: /*foo_p=*/ to annotate bool arguments

> On Oct 5, 2016, at 12:12 PM, Jeff Law wrote: > > On 10/04/2016 03:08 PM, Jason Merrill wrote: >> On Tue, Oct 4, 2016 at 4:29 PM, Zan Lynx wrote: >> ... >> In GCC sources, I think users look at the function definition more >> often than the declaration in the header, the latter of which >> typ

Re: Suboptimal bb ordering with -Os on arm

> On Nov 10, 2016, at 8:16 PM, Nicolai Stange wrote: > ... > >> There is no way to ask for somewhat fast and somewhat small at the >> same time, which seems to be what you want? > > No, I want small, possibly at the cost of performance to the extent of > what's sensible. What sensible actually

Re: Adoption of C subset standards

> 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: Adoption of C subset standards

> 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: Adoption of C subset standards

> 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: Release Signing Keys are Susceptible to Attack

> On Aug 17, 2017, at 4:39 AM, Richard Biener > wrote: > > On Thu, Aug 17, 2017 at 4:23 AM, R0b0t1 wrote: >> After downloading and verifying the releases on >> ftp://ftp.gnu.org/gnu/, I found that the maintainers used 1024 bit DSA >> keys with SHA1 content digests. 1024 bit keys are considered

Re: Overwhelmed by GCC frustration

> On Aug 17, 2017, at 11:22 AM, Oleg Endo wrote: > > On Wed, 2017-08-16 at 19:04 -0500, Segher Boessenkool wrote: >> >> LRA is easier to work with than old reload, and that makes it better >> maintainable. >> >> Making LRA handle everything reload did is work, and someone needs to >> do it. >

Re: Overwhelmed by GCC frustration

> On Aug 17, 2017, at 1:36 PM, Bin.Cheng wrote: > > On Thu, Aug 17, 2017 at 6:22 PM, wrote: >> >> ... >> One of GCC's great strength is its support for many ISAs. Not all to the >> same level of excellence, but there are many, and adding more is easy at >> least for an initial basic level

Re: Power 8 in-core crypto not working as expected

> On Sep 7, 2017, at 10:35 AM, Jeffrey Walton wrote: > > On Thu, Sep 7, 2017 at 4:38 AM, Segher Boessenkool > wrote: >> Hi! >> >> On Thu, Sep 07, 2017 at 12:37:33AM -0400, Jeffrey Walton wrote: >>> I have implementation for AES on Power 8 using GCC's built-ins. Its >>> available for inspection

Re: Byte swapping support

> On Sep 12, 2017, at 5:32 AM, Jürg Billeter > wrote: > > Hi, > > To support applications that assume big-endian memory layout on little- > endian systems, I'm considering adding support for reversing the > storage order to GCC. In contrast to the existing scalar storage order > support for st

Re: Byte swapping support

> On Sep 13, 2017, at 5:51 AM, Jürg Billeter > wrote: > > On Tue, 2017-09-12 at 08:52 -0700, H.J. Lu wrote: >> Can you use __attribute__ ((scalar_storage_order)) in GCC 7? > > To support existing large code bases, the goal is to reverse storage > order for all scalars, not just (selected) stru

Re: Potential bug on Cortex-M due to used registers/interrupts.

> On Nov 16, 2017, at 11:54 AM, Vitalijus Jefišovas wrote: > > On Cortex-M mcu’s, when interrupt happens, NVIC copies r0-r3 and couple > other registers onto the psp stack, and then jumps to interrupt routine, > when it finishes, NVIC restores these registers, and jumps back to user’s > functio

Re: Request for data

The TZ project, which maintains the timezone database, would be a good place to find pointers. They don't actually manage that information, but pointers to "shape files" that translate map coordinates into the timezone identifier are available. paul > On Dec 14, 2017, at 2:44 PM, Eric

Re: Status of m32c target?

> On Jan 22, 2018, at 5:17 AM, Trevor Saunders wrote: > > On Mon, Jan 22, 2018 at 10:57:35AM +0100, Martin Jambor wrote: >> Hi, >> >> On Fri, Jan 19 2018, Sandra Loosemore wrote: >>> On 01/19/2018 10:14 AM, Jeff Law wrote: >>> cc0 needs to die. That doesn't mean that any particular targ