Re: GCC Git hooks

[Joseph Myers]

On Sun, 15 Sep 2019, Gerald Pfeifer wrote:

> Let me know how I can help, and I will do my best.  (Even if I'll be
> offline most of the next three weeks, I can get online most days and
> spend some time.)

Apart from general review of the test conversion / conversion and hook 
scripts, which everyone can do, I think the main thing would be to advise 
on what needs to happen to avoid breaking the www.gnu.org copy of the site 
and your HTML validation system for commits.

-- 
Joseph S. Myers
jos...@codesourcery.com

Re: GCC Git hooks

[Gerald Pfeifer]

On Sun, 15 Sep 2019, Joseph Myers wrote:
> Apart from general review of the test conversion / conversion and hook 
> scripts, which everyone can do, I think the main thing would be to advise 
> on what needs to happen to avoid breaking the www.gnu.org copy of the site 
> and your HTML validation system for commits.

I reached out to the GNU webmasters for the former.  

On the latter, let's just flip the switch whenever you're ready, and I'll 
see to adjust my script within a day or two and manually perform checks 
until that's done.  (If you can create a sample e-mail notification for 
me, I'll use that to start looking into it.)

Thanks,
Gerald

gcc-10-20190915 is now available

[gccadmin]

Snapshot gcc-10-20190915 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/10-20190915/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 10 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 275736

You'll find:

 gcc-10-20190915.tar.xz   Complete GCC

  SHA256=cedb94d5a0478cfab3daf2691b1444f89f2752bee3f3d3dc5b6c2745ed7b97fa
  SHA1=784a17902dcbd3b6c3e57d9cf2815802e3a0ee98

Diffs from 10-20190908 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-10
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.

[PATCH] RFC: Start discussion on class or classes for thread data in GCC multithreading effort

[Nicholas Krause]

From: npkrause 

This is not meant to be merged nor follow any GCC coding standards
but start the work discussed about multithreading GCC. The dicussion
or part of it is about using per thread versions of the shared
data structures. However this runs into three issues to my knowledge
and therefore need to be dicussed. Some of this was discussed at
Cauldron but Richard was not there so I would like his comments.
1. Stack Size in the pthread spec seems to be a limit of 16K but
can we assume more to allocate the rather large structures into the
thread TLS.
2. Does the data need to be around per GIMPLE passes or for the
whole compilation as if not I would suggest a set of different
classes per GIMPLE,RTL phases.
3. Are the data structures immutable outside of the creation of
the data or do we need to be able to change the data on the fly?

Signed-off-by: npkrause 
---
 gcc/thread-data.c |  8 
 gcc/thread-data.h | 28 
 2 files changed, 36 insertions(+)
 create mode 100644 gcc/thread-data.c
 create mode 100644 gcc/thread-data.h

diff --git a/gcc/thread-data.c b/gcc/thread-data.c
new file mode 100644
index 000..d0fe4c5d511
--- /dev/null
+++ b/gcc/thread-data.c
@@ -0,0 +1,8 @@
+#include "thread-data.h"
+
+ThreadData::ThreadData() {
+
+}
+
+ThreadData::~ThreadData() {
+}
diff --git a/gcc/thread-data.h b/gcc/thread-data.h
new file mode 100644
index 000..0c83846d046
--- /dev/null
+++ b/gcc/thread-data.h
@@ -0,0 +1,28 @@
+/* thread-data.h - Various declarations for data structures to be lauched
+   per thread as found in thread-data.c
+   Copyright (C) 1998-2019 Free Software Foundation, Inc.
+
+This file is part of GCC.
+
+GCC is free software; you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free
+Software Foundation; either version 3, or (at your option) any later
+version.
+
+GCC is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or
+FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+for more details.
+
+You should have received a copy of the GNU General Public License
+along with GCC; see the file COPYING3.  If not see
+.  */
+
+#ifndef GCC_THREAD_DATA_H
+#define GCC_THREAD_DATA_H
+
+class ThreadData {
+   public:
+   ThreadData();
+   ~ThreadData();
+}
-- 
2.20.1