On Wed, 23 May 2018, Richard Biener wrote:
> Yeah. Not sure if we need sth other than FLOAT_MODE or if avoiding the
> chaining in wider mode and friends is enough. I guess one could also
> change IFmode to be a non-scalar, composite mode - a different 'kind' of
> complex mode maybe...
I'm pret
This patch removes several incorrectly documented functions from the "PowerPC
AltiVec Built-in Functions" section of the "Using the GNU Compiler Collection"
manual.
The following two functions are removed because they are not implemented:
vector float vec_copysign (vector float);
vector floa
On Wed, May 23, 2018 at 11:39:37AM -0700, Carl Love wrote:
> > > --- a/gcc/testsuite/gcc.target/powerpc/builtins-1-be.c
> > > +++ b/gcc/testsuite/gcc.target/powerpc/builtins-1-be.c
> > > @@ -1,4 +1,4 @@
> > > -/* { dg-do compile { target { powerpc64-*-* } } } */
> > > +/* { dg-do compile { target {
This was reported over on the older gcc@ list.
Essentially the soft-float code for m68k mis-handles the sign bit for
32bit floating point addition when one or both arguments is infinity.
Essentially we try to extract the sign bit from a saved copy of the
input value. However we saved the input v
On 05/23/2018 05:01 PM, H.J. Lu wrote:
On Tue, May 22, 2018 at 11:55 AM, Luis Machado wrote:
On 05/16/2018 08:18 AM, Luis Machado wrote:
On 05/16/2018 06:08 AM, Kyrill Tkachov wrote:
On 15/05/18 12:12, Luis Machado wrote:
Hi,
On 05/15/2018 06:37 AM, Kyrill Tkachov wrote:
Hi Luis
On 03/20/2018 04:01 PM, Jozef Lawrynowicz wrote:
> Trunk doesn't build for msp430 due to an ICE whilst building libstdc++.
>
> The following patch proposed a while ago fixes the issue, but hasn't been
> applied: https://gcc.gnu.org/ml/gcc-patches/2017-08/msg01433.html
>
> I don't have write acces
On Wed, May 23, 2018 at 3:29 PM, Luis Machado wrote:
>
>
> On 05/23/2018 05:01 PM, H.J. Lu wrote:
>>
>> On Tue, May 22, 2018 at 11:55 AM, Luis Machado
>> wrote:
>>>
>>>
>>>
>>> On 05/16/2018 08:18 AM, Luis Machado wrote:
On 05/16/2018 06:08 AM, Kyrill Tkachov wrote:
>
On Wed, May 23, 2018 at 3:35 PM, H.J. Lu wrote:
> On Wed, May 23, 2018 at 3:29 PM, Luis Machado wrote:
>>
>>
>> On 05/23/2018 05:01 PM, H.J. Lu wrote:
>>>
>>> On Tue, May 22, 2018 at 11:55 AM, Luis Machado
>>> wrote:
On 05/16/2018 08:18 AM, Luis Machado wrote:
>
>
>>>
On Wed, May 23, 2018 at 3:41 PM, H.J. Lu wrote:
> On Wed, May 23, 2018 at 3:35 PM, H.J. Lu wrote:
>
>>>
>>> Sorry. Does the following fix it for i686?
>>>
>>
>> Index: gcc/tree-ssa-loop-prefetch.c
>> ===
>> --- gcc/tree-ssa-loop-pref
Implement TARGET_WARN_FUNC_RETURN for msp430-elf, to eliminate warnings when
functions with the "naked" attribute do not return.
The GCC testsuite completes with no regressions for msp430-elf, and this fixes
pr53633.
If the patch is acceptable, I would appreciate it if someone could commit it
for
Move duplicated code to new _S_string_from_iter function and fix
constraints to accept iterators with const value type.
* include/bits/fs_path.h (path::__is_encoded_char): Change from class
template to alias template.
(path::__value_type_is_char): Use remove_const_t.
The attached patch enhances the get_size_range() function to
extract more accurate ranges out of MIN_EXPR and MAX_EXPR nodes
with SSA_NAME operand(s). This helps -Wstringop-overflow avoid
false positives on some targets in cases like some of those
reported in bug 85623 - strncmp() warns about att
On 05/23/2018 07:42 PM, H.J. Lu wrote:
On Wed, May 23, 2018 at 3:41 PM, H.J. Lu wrote:
On Wed, May 23, 2018 at 3:35 PM, H.J. Lu wrote:
Sorry. Does the following fix it for i686?
Index: gcc/tree-ssa-loop-prefetch.c
===
--- gc
Hi,
On Wed, May 23, 2018 at 08:35:49PM +, Joseph Myers wrote:
> On Wed, 23 May 2018, Michael Meissner wrote:
>
> > One of the problems I've faced over the years is the assumption that there
> > is
> > only one type for a given size, and that isn't true for IF/KF/TFmode.
>
> I think that's a
On Thu, 24 May 2018, Segher Boessenkool wrote:
> Which semantics doesn't it have? (Other than the lack of non-default
> rounding modes, or is that what you meant?)
It has problems with rounding modes, exceptions and various operations
involving large or small arguments or results. Some of thes
The attach patch fixes PR fortran/85895 and also addresses
a nearby issue by resolving the expressions associated with
the STAT= and ERRMSG= tags in SYNC statements. OK to commit?
2018-05-23 Steven G. Kargl
PR fortran/85895
* resolve.c (resolve_sync): Resolve expression before
On Wed, May 23, 2018 at 08:38:21PM +, Joseph Myers wrote:
> On Wed, 23 May 2018, Richard Biener wrote:
>
> > Yeah. Not sure if we need sth other than FLOAT_MODE or if avoiding the
> > chaining in wider mode and friends is enough. I guess one could also
> > change IFmode to be a non-scalar, c
Subject says it all. OK to commit?
2018-05-23 Steven G. Kargl
PR fortran/85779
*decl.c (gfc_match_derived_decl): Fix NULL point dereference.
2018-05-23 Steven G. Kargl
PR fortran/85779
* gfortran.dg/pr85779_1.f90: New test.
* gfortran.dg/pr85779_2.
On 05/21/2018 09:05 AM, Nicolas Koenig wrote:
Hey everyone,
Thomas and I have been working on adding asynchronous I/O to
libgfortran. The patch is almost done, the only thing still missing is
to link libgfortran against libpthread if it exists(which is for some
reason necessary despite using
On 05/23/2018 04:50 PM, Luis Machado wrote:
> On 05/23/2018 07:42 PM, H.J. Lu wrote:
>> On Wed, May 23, 2018 at 3:41 PM, H.J. Lu wrote:
>>> On Wed, May 23, 2018 at 3:35 PM, H.J. Lu wrote:
>>>
>
> Sorry. Does the following fix it for i686?
>
Index: gcc/tree-ssa-loop-prefetch.
Ping for the following C patch sent on 4/22/2018
https://gcc.gnu.org/ml/gcc-patches/2018-04/msg01034.html
Thanks,
--Dave
==
On 04/22/2018 12:17 PM, dave.pa...@oracle.com wrote:
This patch fixes handling of -Werror=return-type as well as
-Wno-return-type. Currently, -Werror=return-typ
101 - 121 of 121 matches
Mail list logo
