On Sep 30 2019, Jerry DeLisle wrote:
> The first attempt to fix (above) is completely off. I have tried various
> combinations of code changes and I am beginning to think the warning is
> bogus:
>
> In function ‘btoa_big’,
> inlined from ‘write_b’ at ../../../trunk/libgfortran/io/write.c:121
Dear Sir
I am from Xi'an, China. We are very interested in your mineral water and look
forward to working with you for a long time! Please send me a picture or quote.
Best regards
Ms Ariel
Mol:0086-13022879793
--
* Gaius Mulley:
> gm2 does use GNU libpth (to create context and switch contexts).
> Although it doesn't need libpth for single process programs. I think
> the GNU libpth project is no longer maintained, so I've included it in:
>
> http://git.savannah.gnu.org/cgit/gm2.git/tree/gcc-versionno/libgm
On 23/09/2019 15:39, Andrew Stubbs wrote:
On 23/09/2019 15:15, Segher Boessenkool wrote:
On Mon, Sep 23, 2019 at 11:56:27AM +0100, Andrew Stubbs wrote:
[(set (match_operand:DI 0 "register_operand" "=Sg,v")
(ashift:DI
(match_operand:DI 1 "gcn_alu_operand" " Sg,v")
Florian Weimer writes:
> * Gaius Mulley:
>
>> gm2 does use GNU libpth (to create context and switch contexts).
>> Although it doesn't need libpth for single process programs. I think
>> the GNU libpth project is no longer maintained, so I've included it in:
>>
>> http://git.savannah.gnu.org/cgit
* Gaius Mulley:
>> The question is whether this is really necessary. Obviously, there is
>> no requirement to ship all supporting code under the GPL version 3 or
>> later for GCC. See the libffi subdirectory, which has its own
>> license.
>
> sure I think it is looking sensible to stop using lib
Florian Weimer writes:
> * Gaius Mulley:
>
>>> The question is whether this is really necessary. Obviously, there is
>>> no requirement to ship all supporting code under the GPL version 3 or
>>> later for GCC. See the libffi subdirectory, which has its own
>>> license.
>>
>> sure I think it is
On 30.09.19 18:46, Gaius Mulley wrote:
again is this sensible? Are there [obvious] issues I've missed?
does the profiled LTO build now work? I didn't check recently myself.
Matthias
Hi,
I have a proposal for making changes to the rules for
compatibility of tagged types in C2X (N2366). This was
received with interest by WG14, so there is a chance
that this could get accepted into C2X.
In particular, the idea is to make structs (+ unions, enums)
with the same tag and the sa
ah no - lto builds fine. But with make profiledbootstrap
it errors out with:
gm2/gm2-libs-boot/pthdummy.o: In function `pth_init':
/home/gaius/GM2/graft-trunk/build-lto-trunk/gcc/../../gcc-versionno/gcc/gm2/gm2-libs-ch/pthdummy.c:48:
undefined reference to `__gcov_indirect_call'
the positive is
On 9/30/19 9:40 PM, Jerry DeLisle wrote:
Copying gcc list for additional thoughts on a possible bogus warning.
On 9/29/19 9:02 AM, Jerry DeLisle wrote:
Hi all,
--- snip ---
diff --git a/libgfortran/io/write.c b/libgfortran/io/write.c
index 4ef35561fdd..fc046efbe34 100644
--- a/libgfortran/i
On 9/20/19 7:18 PM, co...@sdf.org wrote:
> On Fri, Sep 20, 2019 at 10:07:59PM +, co...@sdf.org wrote:
>> Introducing the reversed jbb* patterns doesn't seem to help with the
>> original issue. It crashes building libatomic.
>
> My loose understanding of what is going on:
> - GCC emits this ato
On 9/21/19 12:27 PM, Paul Koning wrote:
>
>
>> On Sep 20, 2019, at 9:18 PM, co...@sdf.org wrote:
>>
>> On Fri, Sep 20, 2019 at 10:07:59PM +, co...@sdf.org wrote:
>>> Introducing the reversed jbb* patterns doesn't seem to help with the
>>> original issue. It crashes building libatomic.
>>
>> M
On 9/30/19 9:40 PM, Jerry DeLisle wrote:
Copying gcc list for additional thoughts on a possible bogus warning.
On 9/29/19 9:02 AM, Jerry DeLisle wrote:
Hi all,
--- snip ---
diff --git a/libgfortran/io/write.c b/libgfortran/io/write.c
index 4ef35561fdd..fc046efbe34 100644
--- a/libgfortran/i
I'm working on structure reorganization optimizations and one of the
things that needs to happen is that pointers to arrays of structures
need to be modified into either being an integer of a structure depending
on which optimization is required.
I'm seeing something similar happening in omp-low.c
On Tue, Oct 01, 2019 at 01:12:06PM +0100, Andrew Stubbs wrote:
> On 23/09/2019 15:39, Andrew Stubbs wrote:
> >On 23/09/2019 15:15, Segher Boessenkool wrote:
> >>On Mon, Sep 23, 2019 at 11:56:27AM +0100, Andrew Stubbs wrote:
> >>> [(set (match_operand:DI 0 "register_operand" "=Sg,v")
> >>>
On 10/1/19 12:40 PM, Martin Sebor wrote:
On 9/30/19 9:40 PM, Jerry DeLisle wrote:
Copying gcc list for additional thoughts on a possible bogus warning.
On 9/29/19 9:02 AM, Jerry DeLisle wrote:
--- snip ---
In case it helps, the warning is for the access:
# .MEM_68 = VDEF <.MEM_71>
ME
17 matches
Mail list logo