Committed.
I hope that's about it, then as far as stray references to GCJ
or libgcj/libjava to...
Gerald
2017-01-23 Gerald Pfeifer
* patch_tester.sh (TESTLOGS): Remove
$TARGET/libjava/testsuite/libjava.sum.
Index: patch_tester.sh
===
Applied (as revision 244769).
Gerald
2017-01-22 Gerald Pfeifer
* doc/xml/manual/debug.xml: code.google.com uses https now.
Index: doc/xml/manual/debug.xml
===
--- doc/xml/manual/debug.xml(revision 244769)
+++ doc/xm
Hi Gerald,
cp2k moved to https://www.cp2k.org/ , but isn't running a nightly gcc trunk
tester anymore. So, yes, patch is OK, unfortunately.
Joost
This is the last patch in the series. It adds logic to handle
non-constant width and precision with range information to help
reduce both false positives false negatives. The patch replaces
the scalar width and precision with two element arrays throughout
the pass and makes adjustments to reflec
The substance of the attached change set is to lay the groundwork
of consolidating the handling of format directives and conversion
specifications.
1) Extend (and rename) struct conversion_spec used thus far to
represent a format conversion specification (the part of the format
string that starts
The attached patch is the last of the refactoring/restructuring
series. It consists of the following changes:
1) Introduce a single global variable, warn_level, that the pass
uses to test the level of the warning that applies to the function
currently being processed (i.e., either -Wformat-overf
This is a resubmission of the patch originally posted before
the holidays, but now split up into smaller change sets to make
review easier. The substance of the changes is described in
the original post:
https://gcc.gnu.org/ml/gcc-patches/2016-12/msg01892.html
The changes are broken up into a
The attached simple patch removes the format_result::constant member
that is not used except in debugging dumps. Removing it makes
the handling of non-constant arguments simpler. Since this handling
increases in the substantive changes that follow this change reduces
the complexity of those chan
On Jan 13, 2017, Jason Merrill wrote:
> On 09/23/2016 08:41 PM, Alexandre Oliva wrote:
>> +static tree global_friend_list;
> This should be a hash_set rather than a TREE_LIST.
You sure? At least in the libcc1 use scenario, this is going to have a
single entry. I didn't even have to make it a
On Sun, 2 Oct 2016, Andreas Schwab wrote:
> Things we may want to remove:
>
> - references to java in contrib (download_ecj, gcc_update,
> patch_tester.sh, update-copyright.py)
I have taken care of these (patch_tester.sh to follow shortly)...
> - GCJ, GCJ_FOR_BUILD, GCJ_FOR_TARGET in Makefiles
> 2017-01-22 Thomas Koenig
>
>* arith.c (arith_power): If simplifying integer power expression
>to zero, warn if -Winteger-division is given.
>
> 2017-01-22 Thomas Koenig
>
>* gfortran.dg/integer_exponentiation_7.f90: New test.
The idea seems reasonable, but I am
Applied, and that's about the last change related to the removal
of GCJ/libgcj from GCC. Phew.
Gerald
2017-01-22 Gerald Pfeifer
* warn_summary: Remove the -java option.
Index: warn_summary
===
--- warn_summary(r
Committed as revision 244765.
Gerald
2017-01-22 Gerald Pfeifer
* doc/xml/manual/test.xml: Fix link into gccint online manual.
Index: doc/xml/manual/test.xml
===
--- doc/xml/manual/test.xml (revision 244759)
+++ doc/
This avoid a redirect, and the trailing slash is technically not
needed (per the specification).
Applied, and not queued for a backport.
Gerald
2017-01-22 Gerald Pfeifer
* doc/install.texi (Specific): opensource.apple.com uses https
now. Remove trailing slash.
Index: doc/in
Hi Joost, Fortran guys,
cp2k.berlios.de seems gone; do we need to remove this link on
https://gcc.gnu.org/benchmarks/ or is there an alternate address
we can use?
Gerald
Index: benchmarks/index.html
===
RCS file: /cvs/gcc/wwwdocs/ht
There was a redirect put in place; let's follow that.
Committed.
Gerald
Index: readings.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.254
diff -u -r1.254 readings.html
--- readings.html 28 De
Hi Jakub,
That's OK - thanks
Paul
On 22 January 2017 at 20:38, Jakub Jelinek wrote:
> Hi!
>
> OpenMP 4.5 allows !$omp declare simd, !$omp declare target and !$omp simd
> in pure and elemental procedures. Fixed thusly, bootstrapped/regtested on
> x86_64-linux and i686-linux, committed to trunk.
Hi!
OpenMP 4.5 allows !$omp declare simd, !$omp declare target and !$omp simd
in pure and elemental procedures. Fixed thusly, bootstrapped/regtested on
x86_64-linux and i686-linux, committed to trunk.
2017-01-22 Jakub Jelinek
PR fortran/79154
* parse.c (matchs, matcho, matchd
On 22.01.2017 19:12, NightStrike wrote:
> On Sun, Jan 22, 2017 at 1:00 PM, Matthias Klose wrote:
>> NightStrike proposed to revert to the 1.2.8 release until zlib stabilizes
>> again;
>> I'm open for that, but didn't want to stay with the 1.2.10 release.
>
> I don't recall making that proposal.
In my opinion, all/most of these should be restored.
On 01/22/2017 08:51 AM, Gerald Pfeifer wrote:
On Fri, 30 Sep 2016, Andrew Haley wrote:
Note I did not include all the removed java/* contents. Is there
anything particular you'd like to retain there?
No, please delete it all.
Okay, so I (
And here is more or less the last patch in this series, removing
java/libgcj2.html and two images (gcj.jpg and swingshot.png).
The only thing left in wwwdocs is a potential merge of java/news.html
into our general news.html that I am considering. That'd take a bit
more time, and I'll see whether
On Sun, Jan 22, 2017 at 1:00 PM, Matthias Klose wrote:
> NightStrike proposed to revert to the 1.2.8 release until zlib stabilizes
> again;
> I'm open for that, but didn't want to stay with the 1.2.10 release.
I don't recall making that proposal. I thought I just suggested that
since modern zli
On 12.01.2017 22:39, Jeff Law wrote:
> On 01/12/2017 02:26 PM, Matthias Klose wrote:
>> On 12.01.2017 22:17, Jeff Law wrote:
>>> On 01/05/2017 07:45 AM, Matthias Klose wrote:
These are the changes updating zlib from 1.2.8 to 1.2.10. It is only used
when
building without a system zli
On Fri, 30 Sep 2016, Andrew Haley wrote:
>> Note I did not include all the removed java/* contents. Is there
>> anything particular you'd like to retain there?
> No, please delete it all.
Okay, so I (finally) went ahead and removed all of java/papers:
cvs commit: Examining java/papers
cvs commit
On 2017.01.22 at 17:20 +0100, Gerald Pfeifer wrote:
> On Sun, 1 Jan 2017, Gerald Pfeifer wrote:
> > When I updated those URLs in June 2015, I must have missed these
> > references in libstdc++ land.
> >
> > Fixed thusly (via revision 244001), and I plan on backporting to
> > GCC 6 and possibly GC
On Sun, 1 Jan 2017, Gerald Pfeifer wrote:
> When I updated those URLs in June 2015, I must have missed these
> references in libstdc++ land.
>
> Fixed thusly (via revision 244001), and I plan on backporting to
> GCC 6 and possibly GCC 5 later.
>
> Gerald
>
> 2017-01-01 Gerald Pfeifer
>
>
http://www.x86-64.org has been dead for a while, so keep the
textual reference, but remove the link.
Committed.
Gerald
Index: gcc-3.1/changes.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-3.1/changes.html,v
retrieving revision 1.70
On 22 January 2017 at 17:57, Tim Song wrote:
> On Sun, Jan 22, 2017 at 10:42 AM, Ville Voutilainen
> wrote:
>> + _GLIBCXX14_CONSTEXPR
>> + bool
>> + operator()(_Tp* __x, _Tp* __y) const
>> + { return uintptr_t(__x) > uintptr_t(__y); }
>
> These reinterpret_casts can't possibly
On Sun, Jan 22, 2017 at 10:42 AM, Ville Voutilainen
wrote:
> + _GLIBCXX14_CONSTEXPR
> + bool
> + operator()(_Tp* __x, _Tp* __y) const
> + { return uintptr_t(__x) > uintptr_t(__y); }
These reinterpret_casts can't possibly be constexpr.
Simple test case:
#include
constexpr b
On Sun, 22 Jan 2017, Rainer Orth wrote:
> right, both IRIX and Tru64 UNIX support were removed after GCC 4.7,
> so this can certainly go.
Thanks for the quick response and confirmation, Rainer!
I got a little confused since https://gcc.gnu.org/gcc-4.7/changes.html
mentions deprecations, but http
On Sun, 22 Jan 2017, Jan Hubicka wrote:
>> Below you find Dimitry's patch with a ChangeLog I created. Bootstrapped
>> on x86_64-unknown-freebsd11.0, and I can take care of committing.
>> 2017-01-21 Dimitry Andric
>>
>> * gcov.c (INCLUDE_ALGORITHM): Define.
>> (INCLUDE_VECTOR): Defin
Tested on Linux-x64.
The tests apparently would never fail unless the arrays are global
and the pointer arithmetic local. However, these tests should
ensure that the results are the same regardless of optimizations,
and these test fail with the current compiler unless the specializations
are prese
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the French team of translators. The file is available at:
http://translationproject.org/latest/gcc/fr.po
(This file, 'gcc-7.1-b20170101.fr.po', h
Hi Gerald,
> Looking through README.Portability I noticed what feels like
> an obsolete reference to Irix 6. Do we really support that,
> or versions that feature this issue, any longer?
>
> Rainer, I think you may have been the last Irix contributor/
> tester we've had?
>
> (The last entry I cou
Looking through README.Portability I noticed what feels like
an obsolete reference to Irix 6. Do we really support that,
or versions that feature this issue, any longer?
Rainer, I think you may have been the last Irix contributor/
tester we've had?
(The last entry I could find was in gcc-4.7/bui
> Honza, Nathan,
>
> On Sat, 21 Jan 2017, Dimitry Andric wrote:
> > As discussed with the FreeBSD gcc ports maintainer [1], building trunk
> > gcc with libc++ requires standard C++ headers to be included *before*
> > gcc/system.h, otherwise the redefinition of abort() to fancy_abort()
> > will cau
Hello world,
a reacent thread on c.l.f showed another common error - expecting
10**(-3) to expect something different from zero. The attached
patch warns about this result if -Winteger-division is active.
Why -Winteger-division? Two reasons: First, 10**(-3) ist just
a shorthand for integer di
Hi David,
On Fri, 14 Oct 2016, David Malcolm wrote:
> I propose that we update our coding conventions to mention the OVERRIDE
> and FINAL macros in the paragraph that discusses virtual funcs.
>
> The attached patch (to the website) does so.
>
> OK to commit?
I saw that Pedro agreed, but none of
38 matches
Mail list logo
