On 2023/10/10 11:11 PM, Andrew Stubbs wrote:
> Hi all,
>
> I'm trying to add a new register set to the GCN port, but I've hit a
> problem I don't understand.
>
> There are 256 new registers (each 2048 bit vector register) but the
> register file has to be divided between all the running hard
On 08/10/2023 15:59, Iain Sandoe wrote:
Hi François,
On 23 Sep 2023, at 21:10, François Dumont wrote:
I'm eventually fixing those tests the same way we manage this problem in
libstdc++ testsuite.
testsuite: Add optional libstdc++ version namespace in expected diagnostic
When lib
Hi Andrew,
On Tue, Oct 10, 2023 at 04:11:18PM +0100, Andrew Stubbs wrote:
> I'm also seeing wrong-code bugs when I allow more than 32 new registers,
> but that might be an unrelated problem. Or the allocation is broken? I'm
> still analyzing this.
It could be connected. both things should not
On Tue, Oct 10, 2023 at 12:09 PM Florian Weimer via Gcc
wrote:
> * Jakub Jelinek:
>
> > On Tue, Oct 10, 2023 at 12:30:52PM -0400, Jason Merrill via Gcc wrote:
> >> On Tue, Oct 10, 2023 at 7:30 AM Florian Weimer via Gcc >
> >> wrote:
> >>
> >> > Are these code fragments valid C89 code?
> >> >
> >
Hi,
I've been looking into existing function multiversioning implementations (while
working to add support for fmv in GCC on aarch64). It seems there are various
inconsistencies among current implementations, and it's unclear to me which (if
any) of these differences could be problematic. There'
* Jason Merrill:
>> But that wasn't really the direction of my question. I was wondering
>> where we should document a future C version of -fpermissive.
>
> My permerror patch proposes moving it to the Warning Options node,
> right after -pedantic-errors.
Yes, that should work. I'm basing my pa
* Joseph Myers:
> On Tue, 10 Oct 2023, Florian Weimer via Gcc wrote:
>
>> Are these code fragments valid C89 code?
>>
>> int i1 = 1;
>> char *p1 = i;
>>
>> char c;
>> char *p2 = &c;
>> int i2 = p2;
>
> Implicit conversions between pointers and integers are not valid C89.
>
> ANSI C89,
* Jakub Jelinek:
> On Tue, Oct 10, 2023 at 12:30:52PM -0400, Jason Merrill via Gcc wrote:
>> On Tue, Oct 10, 2023 at 7:30 AM Florian Weimer via Gcc
>> wrote:
>>
>> > Are these code fragments valid C89 code?
>> >
>> > int i1 = 1;
>> > char *p1 = i;
>> >
>> > char c;
>> > char *p2 = &c;
>>
On Tue, 10 Oct 2023, Florian Weimer via Gcc wrote:
> Are these code fragments valid C89 code?
>
> int i1 = 1;
> char *p1 = i;
>
> char c;
> char *p2 = &c;
> int i2 = p2;
Implicit conversions between pointers and integers are not valid C89.
ANSI C89, as adopted as FIPS PUB 160, is ava
On Tue, Oct 10, 2023 at 12:30:52PM -0400, Jason Merrill via Gcc wrote:
> On Tue, Oct 10, 2023 at 7:30 AM Florian Weimer via Gcc
> wrote:
>
> > Are these code fragments valid C89 code?
> >
> > int i1 = 1;
> > char *p1 = i;
> >
> > char c;
> > char *p2 = &c;
> > int i2 = p2;
> >
> > Or ca
On Tue, Oct 10, 2023 at 7:12 AM Florian Weimer via Gcc
wrote:
> * Richard Earnshaw:
>
> > On 10/10/2023 11:46, Richard Earnshaw (lists) via Gcc wrote:
> >> On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
> >>> Currently, -fsigned-char and -funsigned-char are only documented as C
> >>> language
On Tue, Oct 10, 2023 at 7:30 AM Florian Weimer via Gcc
wrote:
> Are these code fragments valid C89 code?
>
> int i1 = 1;
> char *p1 = i;
>
> char c;
> char *p2 = &c;
> int i2 = p2;
>
> Or can we generate errors for them even with -std=gnu89?
>
> (It will still be possible to override th
Hi all,
I'm trying to add a new register set to the GCN port, but I've hit a
problem I don't understand.
There are 256 new registers (each 2048 bit vector register) but the
register file has to be divided between all the running hardware
threads; if you can use fewer registers you can get mo
Hello,
I am working on a project to produce the LTO object file from the compiler
directly. So far, we have
correctly outputted .symtab along with various .debug sections. The only
thing remaining is to
correctly output attribute values and their corresponding values in the
.debug_info section. Thi
On Tue, Oct 10, 2023 at 2:43 PM Joern Rennecke
wrote:
>
> I'm working on implementing hardware loops for the CORE-V CV32E40P
> https://docs.openhwgroup.org/projects/cv32e40p-user-manual/en/latest/corev_hw_loop.html
>
> This core supports nested hardware lops, but does not allow any other flow
> co
I'm working on implementing hardware loops for the CORE-V CV32E40P
https://docs.openhwgroup.org/projects/cv32e40p-user-manual/en/latest/corev_hw_loop.html
This core supports nested hardware lops, but does not allow any other flow
control inside hardware loops. I found that our existing interfaces
Are these code fragments valid C89 code?
int i1 = 1;
char *p1 = i;
char c;
char *p2 = &c;
int i2 = p2;
Or can we generate errors for them even with -std=gnu89?
(It will still be possible to override this with -fpermissive or
-Wno-int-conversion.)
Thanks,
Florian
On Tue, Oct 10, 2023 at 1:13 PM Florian Weimer via Gcc wrote:
>
> * Richard Earnshaw:
>
> > On 10/10/2023 11:46, Richard Earnshaw (lists) via Gcc wrote:
> >> On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
> >>> Currently, -fsigned-char and -funsigned-char are only documented as C
> >>> languag
* Richard Earnshaw:
> On 10/10/2023 11:46, Richard Earnshaw (lists) via Gcc wrote:
>> On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
>>> Currently, -fsigned-char and -funsigned-char are only documented as C
>>> language options, although they work for C++ as well (and Objective-C
>>> and Objec
On 10/10/2023 11:46, Richard Earnshaw (lists) via Gcc wrote:
> On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
>> Currently, -fsigned-char and -funsigned-char are only documented as C
>> language options, although they work for C++ as well (and Objective-C
>> and Objective-C++, I assume, but I h
On 10/10/2023 10:47, Florian Weimer via Gcc wrote:
> Currently, -fsigned-char and -funsigned-char are only documented as C
> language options, although they work for C++ as well (and Objective-C
> and Objective-C++, I assume, but I have not tested this). There does
> not seem to be a place for thi
Currently, -fsigned-char and -funsigned-char are only documented as C
language options, although they work for C++ as well (and Objective-C
and Objective-C++, I assume, but I have not tested this). There does
not seem to be a place for this kind of options in the manual.
The options -fshort-enums
On Tue, 10 Oct 2023, 08:00 h3140067568--- via Gcc, wrote:
> Hi, I am a Linux development enthusiast who sent you an email last time.
> After compiling glibc, I used make install to display nss_ Test2 cannot
> link the specified installation path to/usr
>
GCC and Glibc are separate projects with
Hi, I am a Linux development enthusiast who sent you an email last time. After
compiling glibc, I used make install to display nss_ Test2 cannot link the
specified installation path to/usr
24 matches
Mail list logo