Snapshot gcc-7-20180712 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180712/
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
On 07/12/2018 04:41 AM, Richard Sandiford wrote:
Following on from:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00603.html
this patch is an RFC to mention references in the C++ coding conventions.
It allows const references anywhere they're useful but only allows
non-constant references i
On Thu, 12 Jul 2018 at 19:01, Pedro Alves wrote:
>
> On 07/12/2018 05:17 PM, Richard Sandiford wrote:
> > Pedro Alves writes:
>
> >> (an
> >>> alternative to pointers is to return a struct with the wide int result
> >>> and the overflow flag),
> >>
> >> +1. I've been pushing GDB in that directio
I tried to rebuild for target pdp11 with fortran enabled (in the past I've just
enabled C). It builds fine but the resulting compiler crashes at startup:
Paul-Konings-MacBook-Pro:gcc pkoning$ ./xgcc -B. -O2 -S ../../hello.f
f951: internal compiler error: gfc_validate_kind(): Got bad kind
libback
On 07/12/2018 05:17 PM, Richard Sandiford wrote:
> Pedro Alves writes:
>> (an
>>> alternative to pointers is to return a struct with the wide int result
>>> and the overflow flag),
>>
>> +1. I've been pushing GDB in that direction whenever possible.
>
> I agree that can sometimes be better. I
Status
==
The GCC 8 branch is open for regression and documentation fixes. We
intend to release GCC 8.2 soon starting with a release candidate
mid to end of next week. This gives you some time to go over your
assigned regression bug reports and consider backports.
There is currently one P
Pedro Alves writes:
> On 07/12/2018 12:40 PM, Jonathan Wakely wrote:
>> On Thu, 12 Jul 2018 at 11:41, Richard Sandiford wrote:
>>> +Only use non-constant references in the following situations:
>>> +
>>> +
>>> +
>>> +when they are necessary to conform to a standard interface, such as
>>> +the firs
On 12/07/18 16:20, Umesh Kalappa wrote:
Hi everyone,
we have our source base ,that was compiled for armv7 on gcc8.1 with
soft-float and for following input
a=0x0010
b=0x0001
result = a - b ;
we are getting the result as "0x000e" and with
-mhard-float (dis
Hi everyone,
we have our source base ,that was compiled for armv7 on gcc8.1 with
soft-float and for following input
a=0x0010
b=0x0001
result = a - b ;
we are getting the result as "0x000e" and with
-mhard-float (disabled the flush to zero mode ) we are getti
On 07/12/2018 12:40 PM, Jonathan Wakely wrote:
> On Thu, 12 Jul 2018 at 11:41, Richard Sandiford wrote:
>> +Only use non-constant references in the following situations:
>> +
>> +
>> +
>> +when they are necessary to conform to a standard interface, such as
>> +the first argument to a non-member ope
On Thu, 12 Jul 2018 at 11:41, Richard Sandiford wrote:
> +Only use non-constant references in the following situations:
> +
> +
> +
> +when they are necessary to conform to a standard interface, such as
> +the first argument to a non-member operator+=
And the return value of such operators (which
On Thu, Jul 12, 2018 at 12:41 PM Richard Sandiford
wrote:
>
> Following on from:
>
> https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00603.html
>
> this patch is an RFC to mention references in the C++ coding conventions.
> It allows const references anywhere they're useful but only allows
> non
Following on from:
https://gcc.gnu.org/ml/gcc-patches/2018-07/msg00603.html
this patch is an RFC to mention references in the C++ coding conventions.
It allows const references anywhere they're useful but only allows
non-constant references in contexts that conform to a standard
interface, or
Thank you Jakub ,the attached patch in the PR86492 fixes the issue.
Appreciate your quick response here .
~Umesh
On Wed, Jul 11, 2018 at 10:17 PM, Jakub Jelinek wrote:
> On Wed, Jul 11, 2018 at 09:48:07PM +0530, Umesh Kalappa wrote:
>> Cc'ed Kyrill.
>
> Mailing list is not the right medium to r
14 matches
Mail list logo
