Re: [PATCH] sockaddr.3type: BUGS: Document that libc should be fixed using a union

2023-03-18 Thread roucaries bastien via Gcc
Hi, I have opened a defect at austin group https://www.austingroupbugs.net/view.php?id=1641 Bastien Le lun. 6 févr. 2023 à 18:45, Eric Blake a écrit : > > On Sun, Feb 05, 2023 at 04:28:36PM +0100, Alejandro Colomar wrote: > > Regardless of the merits of the patch, let's not introduce typos: > >

Re: [GSoC] gccrs Unicode support

2023-03-18 Thread Raiki Tamura via Gcc
Thank you everyone for your advice. Some kinds of names are restricted to unicode alphabetic/numeric in Rust. And the current definition of the table defined in libcpp/ucind.h lacks some rows representing which characters are alphabetic/numeric. But it is not a problem because it seems to be easy t

Re: [GSoC] gccrs Unicode support

2023-03-18 Thread Jonathan Wakely via Gcc
On Sat, 18 Mar 2023, 08:32 Raiki Tamura via Gcc, wrote: > Thank you everyone for your advice. > Some kinds of names are restricted to unicode alphabetic/numeric in Rust. > Doesn't it use the same rules as C++, based on XID_Start and XID_Continue? That should already be supported.

Re: [GSoC] gccrs Unicode support

2023-03-18 Thread Raiki Tamura via Gcc
2023年3月18日(土) 17:47 Jonathan Wakely : > On Sat, 18 Mar 2023, 08:32 Raiki Tamura via Gcc, wrote: > >> Thank you everyone for your advice. >> Some kinds of names are restricted to unicode alphabetic/numeric in Rust. >> > > Doesn't it use the same rules as C++, based on XID_Start and XID_Continue? >

Re: [GSoC] gccrs Unicode support

2023-03-18 Thread Jakub Jelinek via Gcc
On Sat, Mar 18, 2023 at 05:59:34PM +0900, Raiki Tamura wrote: > 2023年3月18日(土) 17:47 Jonathan Wakely : > > > On Sat, 18 Mar 2023, 08:32 Raiki Tamura via Gcc, wrote: > > > >> Thank you everyone for your advice. > >> Some kinds of names are restricted to unicode alphabetic/numeric in Rust. > >> > >

Re: #include cobol

2023-03-18 Thread David Edelsohn via Gcc
On Mon, Feb 27, 2023 at 10:13 AM James K. Lowden wrote: > To the GCC community and GCC Steering Committee: Greetings! > > We at COBOLworx would like GCC to consider our gcobol front-end for > inclusion in the GCC project. We would like to contribute it to the > GNU Toolchain and have it merged

Re: cgraph: does node->inlined_to imply node->clones is non-empty?

2023-03-18 Thread Arsen Arsenović via Gcc
Hi Martin, Thank you for the thorough response, and apologies for replying so late (I'm busy most hours of most workdays nowadays). Martin Jambor writes: > Hello, > > I had been aware of your message even before Martin Liška pointed to it, > but I could not answer the questions without looking

[no subject]

2023-03-18 Thread kskumkum via Gcc
-- .HY

gcc-12-20230318 is now available

2023-03-18 Thread GCC Administrator via Gcc
Snapshot gcc-12-20230318 is now available on https://gcc.gnu.org/pub/gcc/snapshots/12-20230318/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 12 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch

GSoC 2023

2023-03-18 Thread ANKESH PANDEY .
Hello, I am Ankesh Pandey, a 3rd year Computer Science Undergraduate. I am interested in contributing for the following projects: 1. Unicode support: Our Lexer and AST do not support Unicode strings and identifiers, which we need to be a Rust compiler. The project will require a stu