[PATCH rs6000] Fix PR86612

2018-07-26 Thread Pat Haugen
Probably an obvious patch but... The testcase fails because it looks like recent glibc headers (2.27 at least) no longer contain a declaration for __strdup, which results in warning messages being generated and failure for excess errors. Fixed by calling the standard name. Verified the testcas

[PATCH] Add a test for std::condition_variable_any

2018-07-26 Thread Marek Polacek
We've been carrying this test internally for quite some time and I think it would be beneficial for everyone to include it in the upstream testsuite, too. Tested on x86_64-linux, ok for trunk and 8.3? 2018-07-26 Marek Polacek * 30_threads/condition_variable_any/cond.cc: New test. ---

Re: [PATCH] Add a test for std::condition_variable_any

2018-07-26 Thread Jonathan Wakely
On 26/07/18 16:03 -0400, Marek Polacek wrote: We've been carrying this test internally for quite some time and I think it would be beneficial for everyone to include it in the upstream testsuite, too. Tested on x86_64-linux, ok for trunk and 8.3? OK. (Although as I said on internal IRC, I don

Re: [PATCH rs6000] Fix PR86612

2018-07-26 Thread Segher Boessenkool
On Thu, Jul 26, 2018 at 02:53:09PM -0500, Pat Haugen wrote: > Probably an obvious patch but... > > The testcase fails because it looks like recent glibc headers (2.27 at least) > no longer contain a declaration for __strdup, which results in warning > messages being generated and failure for exc

Re: [PATCH][Fortran][v2] Use MIN/MAX_EXPR for min/max intrinsics

2018-07-26 Thread Joseph Myers
On Wed, 18 Jul 2018, Janne Blomqvist wrote: > minimumNumber(a, NaN) = minimumNumber(NaN, a) = a > > That is minimumNumber corresponds to minnum in IEEE 754-2008 and fmin* in No, it differs in the handling of signaling NaNs (with minimumNumber, if the NaN argument is signaling, it results in the

Re: [PATCH] treat -Wxxx-larger-than=HWI_MAX special (PR 86631)

2018-07-26 Thread Martin Sebor
On 07/26/2018 08:58 AM, Martin Sebor wrote: On 07/26/2018 02:38 AM, Richard Biener wrote: On Wed, Jul 25, 2018 at 5:54 PM Martin Sebor wrote: On 07/25/2018 08:57 AM, Jakub Jelinek wrote: On Wed, Jul 25, 2018 at 08:54:13AM -0600, Martin Sebor wrote: I don't mean for the special value to be u

Re: Build fail on gthr-simple.h targets (Re: AsyncI/O patch committed)

2018-07-26 Thread Thomas Koenig
Hi Ulrich, The problem is that io/asynch.h unconditionally uses a couple of features that are not provided by gthr-simplex, in particular __gthread_cond_t and __gthread_equal / __gthread_self According to the documentation in gthr.h, the former is only available if __GTHREAD_HAS_COND is d

Re: [PATCH] Merge Ignore and Deprecated in .opt files.

2018-07-26 Thread Joseph Myers
On Thu, 19 Jul 2018, Martin Liška wrote: > I must admit that was my intention :) In my eyes it makes it more consistent > and > it gives consumers feedback about usage of an option that does nothing. > For x86_64 there's list of options that are Ignore and don't produce a > warning: The design

Re: [PATCH] Merge Ignore and Deprecated in .opt files.

2018-07-26 Thread Joseph Myers
On Fri, 20 Jul 2018, Martin Liška wrote: > +C++ ObjC++ Ignore) Stray ')' at the end of this line. -- Joseph S. Myers jos...@codesourcery.com

Re: [0/5] C-SKY port

2018-07-26 Thread Joseph Myers
On Tue, 24 Jul 2018, Sandra Loosemore wrote: > On 07/23/2018 10:17 PM, Sandra Loosemore wrote: > > > C-SKY proposes Han Mao and Yunhai Shang > > as maintainers for this port. > > I apologize, I made a mistake here. The correct proposed maintainers are > Xianmiao Qu and Yunhai Shang > . I'

Re: [PATCH 1/7] Add __builtin_speculation_safe_value

2018-07-26 Thread Joseph Myers
On Wed, 25 Jul 2018, Richard Earnshaw (lists) wrote: > >> Port maintainers DO need to decide what to do about speculation, even if > >> it is explicitly that no mitigation is needed. > > > > Agreed. But I didn't yet see a request for maintainers to decide that? > > > > consider it made, then :

Re: [PATCH 1/7] Add __builtin_speculation_safe_value

2018-07-26 Thread Paul Koning
> On Jul 26, 2018, at 7:34 PM, Joseph Myers wrote: > > On Wed, 25 Jul 2018, Richard Earnshaw (lists) wrote: > Port maintainers DO need to decide what to do about speculation, even if it is explicitly that no mitigation is needed. >>> >>> Agreed. But I didn't yet see a request for

Re: [PATCH 11/11] Increase MAX_MAX_OPERANDS limit

2018-07-26 Thread Dimitar Dimitrov
On Monday, 23/7/2018 16:22:24 EEST Jeff Law wrote: > On 07/19/2018 08:12 PM, Dimitar Dimitrov wrote: > > On събота, 23 юни 2018 г. 20:35:23 EEST Jakub Jelinek wrote: > >> On Sat, Jun 23, 2018 at 03:26:50PM +0300, Dimitar Dimitrov wrote: > >>> I took arm/ldmstm.md as an inspiration. See attached mac

Re: [wwwdocs] PATCH for Re: Create a new mirror

2018-07-26 Thread KoDDoS Mirror
Hello, Gerald, I created a new mirror in Hong Kong. Can you add it too? +Hong Kong: +  http://mirror-hk.koddos.net/gcc/";>http://mirror-hk.koddos.net/gcc/ | +  rsync://mirror-hk.koddos.net/gcc/, +  thanks to Martin (mir...@koddos.net) at KoDDoS. Regards, Martin On Wed, 28 Feb 2018, KoDDoS Mir

Re: [PATCH] Make strlen range computations more conservative

2018-07-26 Thread Bernd Edlinger
I have one more example similar to PR86259, that resembles IMHO real world code: Consider the following: int fun (char *p) { char buf[16]; assert(strlen(p) < 4); //here: security relevant check sprintf(buf, "echo %s - %s", p, p); //here: security relevant code return system(buf); } W

<    1   2