On Thu, Sep 19, 2019 at 7:10 PM Martin Sebor wrote:
>
> All my Fedora 30 builds on x86_64 today have gotten stuck on
> index0-out.x spinning indefinitely. I build and test all
> languages, including Go, so I'm wondering if anyone else who
> builds Go sees the same thing or if you know of a workar
All my Fedora 30 builds on x86_64 today have gotten stuck on
index0-out.x spinning indefinitely. I build and test all
languages, including Go, so I'm wondering if anyone else who
builds Go sees the same thing or if you know of a workaround.
Thanks
Martin
Snapshot gcc-7-20190919 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190919/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
Hi!
Some projects (most notably the linux-kernel) choose to use -Wvla to
warn on
usage of variable length array. The primary reason is usually that it
can
cause stack overflows if the programmer isn't careful, which introduces
a
security vulnerability.
I think an overlooked advantage of VLA's is
> On Sep 17, 2019, at 8:02 AM, Richard Earnshaw (lists)
> wrote:
>
> ...
> So in summary my proposed timetable would be:
>
> Monday 16th December 2019 - cut off date for picking which git conversion to
> use
>
> Tuesday 31st December 2019 - SVN repo becomes read-only at end of stage 3.
>
Thanks to you and Janne for the thoughtful replies. I understand better
the immediate goals now.
Damian
On Thu, Sep 19, 2019 at 08:31 Richard Earnshaw (lists) <
richard.earns...@arm.com> wrote:
> On 19/09/2019 13:04, Janne Blomqvist wrote:
> > On Tue, Sep 17, 2019 at 3:02 PM Richard Earnshaw (l
> On Sep 17, 2019, at 3:02 PM, Richard Earnshaw (lists)
> wrote:
>
> At the Cauldron this weekend the overwhelming view for the move to GIT soon
> was finally expressed.
>
...
>
> So in summary my proposed timetable would be:
>
> Monday 16th December 2019 - cut off date for picking which git
On 19/09/2019 13:04, Janne Blomqvist wrote:
On Tue, Sep 17, 2019 at 3:02 PM Richard Earnshaw (lists)
wrote:
There should be NO CHANGE to the other processes and policies that we
have, eg patch reviews, ChangeLog policies etc at this time. Adding
requirements for this will just slow down the tr
On Thu, Sep 19, 2019 at 5:43 PM Damian Rouson
wrote:
>
>
>
> On Thu, Sep 19, 2019 at 5:04 AM Janne Blomqvist
> wrote:
>>
>>
>> One thing that's unclear to me is how should I actually make my stuff
>> appear in the public repo? Say I want to work on some particular
>> thing:
>
>
> This is essenti
On Thu, Sep 19, 2019 at 5:04 AM Janne Blomqvist
wrote:
>
> One thing that's unclear to me is how should I actually make my stuff
> appear in the public repo? Say I want to work on some particular
> thing:
>
This is essentially a git workflow question. A simple and useful workflow
to consider is
Hello!
Email: g...@gnu.org
Our international company has about 65 Internet projects related
to crypto currencies and ICO. Now we recruit staff from all over the world.
CHECK IT OUT HERE
Primary salary $295k yearly E-workers wanted.
- No Special Skills Needed
- No Previous Job Experience Requi
On Tue, Sep 17, 2019 at 3:02 PM Richard Earnshaw (lists)
wrote:
> There should be NO CHANGE to the other processes and policies that we
> have, eg patch reviews, ChangeLog policies etc at this time. Adding
> requirements for this will just slow down the transition by
> over-complicating things.
Hi.
As slightly discussed at the Cauldron, I would like to announce
more pages linked at gcc.opensuse.org. Following links
can be found on the website:
- We've running SPEC benchmarks in LNT for more than a year
- OBS testing project - I'm build ~40 packages with latest GCC master
on daily basis
On Thu, Sep 19, 2019 at 4:27 AM Gary Oblock wrote:
>
> I'm trying to build new functions on the fly during optimization.
> For those of you that have not been following my previous questions,
> this is structure reorganization optimization related. For example when
> somebody frees an array of typ
On Wed, Sep 18, 2019 at 3:09 PM Bernd Edlinger
wrote:
>
> Hi,
>
> I'm currently trying to add -Wshadow=local to the gcc build rules.
> I started with -Wshadow, but gave up that idea immediately.
>
> As you could expect the current code base has plenty of shadowed
> local variables. Most are trivi
15 matches
Mail list logo