FYI - International Microwave Symposium 2023

Hello Are you interested in purchasing International Microwave Symposium 2023 Updated Database Attendees: Design Engineering, Executive/Senior Management, Student, Professor / Research-Academic, Marketing/Sales, Research & Development-Industry, Engineering Management, Application Engineer, Exe

Re: [Static Analyzer] Loop handling - False positive for malloc-sm

On Mon, 2023-03-20 at 13:28 +0100, Pierrick Philippe wrote: > Hi everyone, > > I'm still playing around with the analyzer, and wanted to have a look > at > loop handling. > I'm using a build from /trunk/ branch (/20230309/). > > Here is my analyzed code: > > ''' > 1| #include > 2| int main(voi

Re: [GSoC][Static Analyzer] First proposal draft and a few more questions/requests

On Mon, 2023-03-20 at 18:28 +0100, Shengyu Huang wrote: > Hi Dave, > > Thanks for always getting back to me so promptly! I am drafting the > proposal today. Here is the link: > > https://docs.google.com/document/d/1MRI1R5DaX8kM6DaqRQsEri5Mx2FvHmWv13qe1W0Bj0g/ > > (The proposal was first written

[GSoC 2023] Rust front-end: Improving User Errors

Greetings, My name is Panagiotis Foliadis, Ι'm 26 years old and I am from Athens, Greece. I'm interesting in the Rust frοnt-end project and especially at Improving user errors. I'm a self taught  software developer with solid knowledge about Rust, and also Ι'm doing my internship that mainly us

[GSOC] query about C++: Implement compiler built-in traits for the standard library traits

Hello Everyone I'm Anastasia. I am a prospective GSOC Student. I wish to know if the project C++: Implement compiler built-in traits for the standard library traits is still available. I have already build and got my hand dirty on debugging GCC. How should I proceed to make a proposal. Also I wa

Re: [GSOC] getting "gdb: unrecognized option '-dumpdir'' while trying to debug gcc using gdb

On Mon, 2023-03-20 at 22:36 +0530, Rishi Raj wrote: > I am sorry for the previous messed-up reply :(. I was trying to reply > back > to my previous mail thread but mistakenly replied to the entire > digest::((. > Thanks, David and Martin, for the heads up, and I am sorry for the > late > reply due

[GSoC][Static Analyzer] First proposal draft and a few more questions/requests

Hi Dave, Thanks for always getting back to me so promptly! I am drafting the proposal today. Here is the link: https://docs.google.com/document/d/1MRI1R5DaX8kM6DaqRQsEri5Mx2FvHmWv13qe1W0Bj0g/ (The proposal was first written in markdown and then copied pasted to Google Docs, so some formatting

[GSOC] getting "gdb: unrecognized option '-dumpdir'' while trying to debug gcc using gdb

I am sorry for the previous messed-up reply :(. I was trying to reply back to my previous mail thread but mistakenly replied to the entire digest::((. Thanks, David and Martin, for the heads up, and I am sorry for the late reply due to health issues. Anyways I could emit the warning "hello world, I

Re: Gcc Digest, Vol 37, Issue 8

Thanks, David and Martin, for the heads up, and I am sorry for the late reply due to health issues. Anyways I could emit the warning "hello world, I am function foo.". After that, I tried debugging using the` ../gcc -wrapper gdb test.c`(gcc binary is in parent folder) but I am getting this error "

[Static Analyzer] Loop handling - False positive for malloc-sm

Hi everyone, I'm still playing around with the analyzer, and wanted to have a look at loop handling. I'm using a build from /trunk/ branch (/20230309/). Here is my analyzed code: ''' 1| #include 2| int main(void) { 3|    void * ptr = malloc(sizeof(int)); 4|    for (int i = 0; i < 10; i++) {

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

Hi Bastien and Eric! On 3/18/23 08:54, roucaries bastien wrote: > Hi, > > I have opened a defect at austin group > https://www.austingroupbugs.net/view.php?id=1641 Sorry for not having prepared yet my report as I promised to Eric. I've been busy with other stuff, but still had in mind doing it :

Re: [GSoC] gccrs Unicode support

2023年3月18日(土) 18:28 Jakub Jelinek : > That is a pretty simple thing, so no need to use an extra library for that. > As is documented in contrib/unicode/README, the Unicode *.txt files are > already checked in and there are several generators of tables. > libcpp/makeucnid.cc already creates tables

RISC-V V C Intrinsic API v1.0 release meeting reminder (March 20th, 2023)

Hi all, A reminder that the next open meeting to discuss on the RISC-V V C Intrinsic API v1.0 is going to be held later on 2023/03/20 6AM (GMT -7) / 11PM (GMT +8). The agenda can be found in the second page of the meeting slides (link