Having trouble getting my school to sign the copyright disclaimer

Hello, I’m trying to get my school to sign the copyright disclaimer. Unfortunately the officials are reluctant to do that. Can anyone suggest what to do next? They claim that university owns copyright to my code if I wrote it for a school-related research project. However, since I’m an undergra

My GSoC proposal for the Rust frontend

It’s about improving compiler dumps for the Rust frontend. Full proposal here:  https://docs.google.com/document/d/1gyAOM-f3RyZh3HVpjmIMDSuQ5gBscal71sFY6XUMcHI/edit# Yizhe

Re: GCC association with the FSF

On Mon, 12 Apr 2021 at 03:13, Chris Punches via Gcc wrote: > Hello, > > I've been reading quietly on how the GCC SC handles this and generally > only lurk here so that I can stay informed on GCC changes. I am nobody > you would probably care about, but, maybe I will be one

Re: removing toxic emailers

Eric S. Raymond : > there is actually a value conflict between being "welcoming" in that sense and the actual purpose of this list, which is to ship code. Speaking as a "high functioning autist", I'm aware of the difficulties that some of us have with social interactions - and also that many of us

Re: removing toxic emailers

On Fri, 16 Apr 2021 at 05:59, Eric S. Raymond wrote: > Ian Lance Taylor : > > Patronizing or infantilizing anybody doesn't come into this at all. > > I am not even *remotely* persuaded of this. This whole attitude that if > a woman is ever exposed to a man with less than perfect American > upper

Re: removing toxic emailers

On Thu, Apr 15, 2021, 23:42 Iain Sandoe via Gcc wrote: > it is essential (IMO) that review of code is carried out on a fair and > technical basis without personal attack or harrassment (or > unwelcome unrelated attention). > Is this not the case on gcc-patches? >

Re: A suggestion for going forward from the RMS/FSF debate

On Fri, Apr 16, 2021 at 7:23 AM Ville Voutilainen via Gcc wrote: > On the first part, other people have touched on it already, > but the fear of a dreaded non-free software vendor co-opting > GCC as a library to a non-free project has resulted in GCC > being unsuitable to be used as

Re: On US corporate influence over Free Software and the GCC Steering Committee

On Tue, 20 Apr 2021 at 11:21, David Brown wrote: > On 20/04/2021 08:54, Giacomo Tesio wrote: > > Hi GCC developers, > > > > just to further clarify why I think the current Steering Committee is > highly problematic, > > I'd like you to give a look at

Re: D build on powerpc broken (was Re: GCC 11.1 Release Candidate available from gcc.gnu.org)

> On 21/04/2021 00:02 Peter Bergner wrote: > > > On 4/20/21 4:20 PM, Jakub Jelinek via Gcc wrote: > > On Tue, Apr 20, 2021 at 03:27:08PM -0500, William Seurer via Gcc wrote: > >> /tmp/cc8zG8DV.s: Assembler messages: > >> /tmp/cc8zG8DV.s:2566: Error: unsuppor

FedEx Tracking

Fed Ex Order: CN-5879-6676543 Dear Customer, An express parcel was sent to you with your email : gcc@gcc.gnu.org you can pick this up at the nearest FEDEX post-office or, it can be delivered to your registered office. VIEW PARCEL DETAILS HERE NOTE THIS MAIL IS NOT "

FedEx Tracking

Fed Ex Order: CN-5879-6676543 Dear Customer, An express parcel was sent to you with your email : gcc@gcc.gnu.org you can pick this up at the nearest FEDEX post-office or, it can be delivered to your registered office. VIEW PARCEL DETAILS HERE NOTE THIS MAIL IS NOT "

Linkitettyä Google-tiliäsi koskeva turvallisuusilmoitus

jukka säntti Osoitteesi gcc@gcc.gnu.org on tilin jukka.hen...@gmail.com palauttamisen sähköpostiosoite. Etkö tunnista tätä tiliä? Klikkaa tätä <https://accounts.google.com/AccountDisavow?adt=AOX8kioqbeIbboPmeeRDXQiHuDg110x28RuyvFEbs9dgYFFUVYaVT1yuRcU&rfn=100&anexp=givab-fa--apa

How to understand the "memory" and the volatile keyword?

Hi, I want to know how to use inline assembler instruction, and wonder what is the meaning of "memory" in clobbered register list. According to the manual of GCC, the "memory" will cause GCC to not keep memory values cached in registers across the assembler instruct

Test announcement

test http://tracking.desktop.al/tracking/unsubscribe?msgid=xuZXM1pE-Fzjv0SRTEY2-Q2

dJqkhS

aXuWtpaAdglWmht JLLghLREjZWVRnjhBGKL

Security alert for your linked Google Account

chandramohananbs mohananbs Your account gcc@gcc.gnu.org is listed as the recovery email for chandramohan...@gmail.com. Don't recognize this account? Click here <https://accounts.google.com/AccountDisavow?adt=AOX8kiqrLyTdn1RkdCgC6vH2QPmPZ4ynJNm6N0hymjWWoQQsxOKDuLoncPQ&rfn=31&ane

Thank you for paying from the Adobe Store. Here are details about your Payment:

October 31 October 31, 2013     Your Payment confirmation           Dear g...@gnu.org           Thank you for paying from the Adobe Store. Here are details about your Payment:           Adobe ID: g...@gnu.org

Susietos „Google“ paskyros saugos įspėjimas

Slaptažodis pakeistas Gavote šį pranešimą, nes gcc@gcc.gnu.org nurodytas kaip zemciugl...@gmail.com atkūrimo el. paštas. Jei zemciugl...@gmail.com nėra jūsų „Google“ paskyra, spustelėkite čia, kad atsijungtumėte <https://accounts.google.com/AccountDisavow?adt=AOX8kire9R5nepWVR9B_g

Susietos „Google“ paskyros saugos įspėjimas

Lena Zemciugova Paskyra gcc@gcc.gnu.org nurodyta kaip zemciugl...@gmail.com atkūrimo el. paštas. Neatpažįstate šios paskyros? Spustelėkite čia <https://accounts.google.com/AccountDisavow?adt=AOX8kiqnB6gfcvgCbqdodu0SP84VeUi5SDBjbqexQafSSMcl8lFpOFjifJU&rfn=91&anexp=rmd-standalon

Susietos „Google“ paskyros saugos įspėjimas

Slaptažodis pakeistas Gavote šį pranešimą, nes gcc@gcc.gnu.org nurodytas kaip zemciugl...@gmail.com atkūrimo el. paštas. Jei zemciugl...@gmail.com nėra jūsų „Google“ paskyra, spustelėkite čia, kad atsijungtumėte <https://accounts.google.com/AccountDisavow?adt=AOX8kioyOMyaXCwDU_Y3bkb4C

How to debug .md file?

Hello,I'm a newbie to GCC.Have done some changes to .md file(specifically peephole.md) and the changes are not taking place.How to debug the .md file ? Thanks!

Workshop on Essential Abstractions in GCC

Workshop on Essential Abstractions in GCC, 2011 (http://www.cse.iitb.ac.in/grc/gcc-workshop-11) --- Organized by: GCC Resource Center (http://www.cse.iitb.ac.in/grc). Venue:Department of Computer Science and

Re: State of AutoFDO in GCC

On Fri, Apr 23, 2021 at 4:16 AM Martin Liška wrote: > > On 4/22/21 9:58 PM, Eugene Rozenfeld via Gcc wrote: > > GCC documentation for AutoFDO points to create_gcov tool that converts > > perf.data file into gcov format that can be consumed by gcc with > > -fauto-prof

Could vector type of poly_int and compile-time constants be enabled at the same time ?

Hi, I have a little know about for 'Sizes and offsets as runtime invariants’, and need to add vector types like V2SImode as compile-time constants with enabled vector types of runtime invariants. Could I enable two vector types at same time ? I guess it’s

Re: Could vector type of poly_int and compile-time constants be enabled at the same time ?

Hi, Okay & got it, Thanks for detail :) Jojo R 在 2021年4月29日 +0800 PM5:11，Richard Sandiford ，写道： > JojoR via Gcc writes: > > Hi, > > > > I have a little know about for 'Sizes and offsets as runtime invariants’, > > > > and need to add vector typ

Re: Could vector type of poly_int and compile-time constants be enabled at the same time ?

Hi, Okay & thanks. Jojo R 在 2021年4月29日 +0800 PM6:28，Richard Biener ，写道： > On Thu, Apr 29, 2021 at 5:40 AM JojoR via Gcc wrote: > > > > Hi, > > > > I have a little know about for 'Sizes and offsets as runtime invariants’, > > > > and need t

[PATCH] libsanitizer: Fix compile error with linux-5.12

From: Guo Ren ../../../../libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:133:10: fatal error: linux/cyclades.h: No such file or directory 133 | #include | ^~ Linux has remove the cyclades driver:

Re: Speed of compiling gimple-match.c

Jojo R 在 2021年5月4日 +0800 PM4:58，Thomas Schwinge ，写道： > Hi! > > On 2021-05-03T13:18:35-0700, Andrew Pinski via Gcc wrote: > > I noticed my (highly, -j24) parallel build of GCC is serialized on > > compiling gimple-match.c. Has anyone looked into splitting this > > g

DW_TAG_compile_unit not generated only for some source

Hello, first of all, congratulation for the amazing compiler that all of you have implemented! Second: I’m using GCC version 4.9.4 for powerpc architecture ( powerpc-eabi-gcc ) and I don’t know why but it seems that the DWARF debug info are generated only for a subset of the

SARS-CoV-2 vaccine (Vero cell)

Dear Purchasing Manager: Hello! We provide you with China Kexing Zhongwei inactivated coronavirus vaccine (Vero cell) , disposable syringes, new cap detection boxes, masks and other anti-epidemic supplies. Best wishes! Company name: Zhejiang Kangyue Medical Technology Co., Ltd Company address: Z

shutterstock

Dear Sir, There are more than 700 illustrations here, find the railway station you need. *https://www.shutterstock.com/g/Amjad+Hossain?rid=230688451&utm_medium=email&utm_source=ctrbreferral-link

Re: Update to GCC copyright assignment policy

On Mon, Jun 7, 2021, 06:12 Giacomo Tesio wrote: > The Steering Committee can avoid all of this, now. > I cannot really understand why they shouldn't. > Likely because the primary contributor to c++ has said he will stop contributing unless the change is made. >

Re: Update to GCC copyright assignment policy

ase. > > Nor to stick with the previous policy for fixes backported to the other > versions. > > I mean, I do not know what's his goal, but I guess he doesn't intend to > blackmail > the Steering Committee and the whole GCC users community to achieve it. > > > Not

[no subject]

Sent from my Samsung Galaxy smartphone.

__fp16 is ambiguous error in C++

#include __fp16 foo (__fp16 a, __fp16 b) { return a + std::exp(b); } compiler options: = riscv64-unknown-linux-gnu-g++ foo.c -march=rv64gc_zfh -mabi=lp64 error: == foo.c: In function '__fp16 foo(__fp16, __fp16)': foo.c:6:23: error: call of overloaded 'exp(__fp16&)' is ambi

Question on tree LIM

Hi, I am investigating one degradation related to SPEC2017 exchange2_r, with loop vectorization on at -O2, it degraded by 6%. By some isolation, I found it isn't directly caused by vectorization itself, but exposed by vectorization, some stuffs for vectorization condition checks are hoisted out a

Re: Question on tree LIM

Hi Richard, on 2021/7/2 下午4:07, Richard Biener wrote: > On Fri, Jul 2, 2021 at 5:34 AM Kewen.Lin via Gcc wrote: >> >> Hi, >> >> I am investigating one degradation related to SPEC2017 exchange2_r, >> with loop vectorization on at -O2, it degraded by 6%. By so

cargo-gccrs - GSoC Progress report

e now able to use `cargo-gccrs` for building and running it. Simply use `cargo gccrs build` or `cargo gccrs run`. ## Problems encountered `gcc` cannot produce multiple binaries with one command: The rust compiler is often invoked by cargo with the goal of generating a binary, a static library

Re: Question on tree LIM

on 2021/7/2 下午7:28, Richard Biener wrote: > On Fri, Jul 2, 2021 at 11:05 AM Kewen.Lin wrote: >> >> Hi Richard, >> >> on 2021/7/2 下午4:07, Richard Biener wrote: >>> On Fri, Jul 2, 2021 at 5:34 AM Kewen.Lin via Gcc wrote: >>>> >>>>

Porting to gcc 11 / intrinsics

When porting to GCC 11, care must be taken to adjust includes of GCC intrinsic headers due to this change: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97148 That should be reflected in: https://gcc.gnu.org/gcc-11/porting_to.html

Analyzer tests fail on windows

David, Many of the analyzer tests fail on windows because they hardcode in the typedef of size_t to be unsigned long. This is not a platform independent definition, though, and is wrong for 64 bit windows. This causes extra warnings that all of the functions using size_t arguments are wrong, becau

Re: Analyzer tests fail on windows

On Mon, Aug 23, 2021 at 4:09 PM David Malcolm wrote: > > On Mon, 2021-08-23 at 09:52 -1000, NightStrike wrote: > > David, > > > > Many of the analyzer tests fail on windows because they hardcode in > > the > > typedef of size_t to be unsigned long. This is not a platform > > independent > > defini

Re: Analyzer tests fail on windows

expected 'void *(long long unsigned int, long long unsigned int)' [-Wbuiltin-declaration-mismatch] * size_t issue gcc.dg/analyzer/gzio-3.c: gcc.dg/analyzer/gzio-3a.c: * For some reason, these work. Maybe fread() isn't a builtin? Maybe there's a way to make gcc emit a warning when fread() is redefined differently.

Re: Porting to gcc 11 / intrinsics

Should I make this a bugzilla? I guess I figured that wouldn't be appropriate. On Mon, Aug 9, 2021, 07:16 NightStrike wrote: > When porting to GCC 11, care must be taken to adjust includes of GCC > intrinsic headers due to this change: > > https://gcc.gnu.org/bugzilla/show

Re: Analyzer tests fail on windows

note: for steps c and f, I needed to include dejagnu in the source tree b/c it wasn't available for me) a) Make a new sysroot with a mingw symlink to the target x86_64-w64-mingw32 b) Build the mingw-w64 headers, install into the sysroot c) Build binutils, install into the sysroot d)

Re: Porting to gcc 11 / intrinsics

On Tue, Aug 24, 2021 at 10:21 PM Andrew Pinski wrote: > > On Tue, Aug 24, 2021 at 6:39 PM NightStrike via Gcc wrote: > > On Mon, Aug 9, 2021, 07:16 NightStrike wrote: > > > > > When porting to GCC 11, care must be taken to adjust includes of GCC > > >

Re: Enable the vectorizer at -O2 for GCC 12

on 2021/8/30 下午10:11, Bill Schmidt wrote: > On 8/30/21 8:04 AM, Florian Weimer wrote: >> There has been a discussion, both off-list and on the gcc-help mailing >> list (“Why vectorization didn't turn on by -O2”, spread across several >> months), about enabling the auto-

How about providing an interface to fusing instructions via scheduling

numerous interfaces in the “GCC INTERNALS” which implement some of my requirements, but all of which just happen not to cover my needs completely. These interfaces are： - bool TARGET_SCHED_MACRO_FUSION_PAIR_P (rtx insn *prev, rtx insn *curr) The name of the interface looks a lot like what I

答复: How about providing an interface to fusing instructions via scheduling

e not matched by the functionality provided by this interface. I don't think it is a good choice to implement my requirements with this interface. -邮件原件- 发件人: Kyrylo Tkachov [mailto:kyrylo.tkac...@arm.com] 发送时间: 2021年9月3日 19:11 收件人: gengqi 抄送: gcc@gcc.gnu.org 主题: RE: How about pr

Delivery report

-Recipient: rfc822;gcc@gcc.gnu.org Action: failed Status: 5.7.1 (delivery not authorized) Remote-MTA: dns;gcc.gnu.org (8.43.85.97) Diagnostic-Code: smtp;550 5.7.1 Blocked by SpamAssassin X-PowerMTA-BounceCategory: spam-related DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim; d=gcc.gnu.org; h

Re: [libc-coord] Add new ABI '__memcmpeq()' to libc

(Android libc maintainer.) should __memcmpeq be in compiler-rt rather than libc? On Thu, Sep 16, 2021 at 1:35 PM Joseph Myers wrote: > On Thu, 16 Sep 2021, Chris Kennelly wrote: > > > In terms of relying on the feature: If __memcmpeq is ever exposed as an > a > > simple alias for memcmp (since

Re: [libc-coord] Add new ABI '__memcmpeq()' to libc

plus testing for _equality_ can (as mentioned earlier) have slightly different properties from the three-way comparator behavior of bcmp()/memcmp(). On Thu, Sep 16, 2021 at 2:43 PM Joseph Myers wrote: > On Thu, 16 Sep 2021, James Y Knight wrote: > > > Wouldn't it be far simpler to just un-deprec

Re: [FYI] bugzilla cleanup

On Thu, Sep 16, 2021 at 11:45 AM Martin Sebor via Gcc wrote: > ice-on-invalid-code: ICE on code that is not syntactically valid. > ice-on-valid-code: ICE on code that is syntactically valid. Presumably, the distinction is there because more attention would get paid to the latter over the

Including documentation files with gcc releases

Have been scrutinising the GCC 11.2 Download. I would appreciate if you start including the gcc source files for the documentation in the release as well.

Including documentation files with gcc releases

I got the GCC 11.2 download, but cannot locate the doc directory used to produce the gcc documentation manuals. ‐‐‐ Original Message ‐‐‐ On Wednesday, October 6th, 2021 at 12:32 PM, Jonathan Wakely wrote: > On Wed, 6 Oct 2021 at 13:07, dimechc via Gcc gcc@gcc.gnu.org wr

Including documentation files with gcc releases

‐‐‐ Original Message ‐‐‐ On Wednesday, October 6th, 2021 at 2:50 PM, Jonathan Wakely wrote: > On Wed, 6 Oct 2021, 14:19 dimechc, wrote: > >> I got the GCC 11.2 download, but cannot locate the doc directory used to >> produce the >> gcc documentation manuals. &g

Including documentation files with gcc releases

than Wakely > > jwakely@gmail.com wrote: > > > > On Wed, 6 Oct 2021, 14:19 dimechc, dime...@protonmail.com wrote: > > > > > I got the GCC 11.2 download, but cannot locate the doc directory used to > > > produce the > > > > > > gcc docu

Voice Notification Message from 3038789299 - name Unavailable 10/18/2021 2:39:43 p.m.

Time: 10/18/2021 2:39:43 p.m. Click attachment to listen to Voice Message

VU#999008: New Vulnerability Report

Hello, Greetings, We have received a report that indicates that one of your products contains a vulnerability. In the interest of coordinated disclosure (which aims to address vulnerabilities before they can be exploited by attackers), we would like to communicate this information to you. To

C-family selftests in language-independant source files

Hi everyone, We have been trying to enable the use of selftests for the rust frontend over at gccrs. While doing this, I have realized that a few tests from language-independant source files such as `opt-problem.c` and `diagnostic.c` actually rely on the compiler being a C one. For example, one t

Re: C-family selftests in language-independant source files

Hi Dave, On 21/11/05 09:23AM, David Malcolm wrote: > On Fri, 2021-11-05 at 10:38 +0100, cohenarthur.dev via Gcc wrote: > > Hi everyone, > > > > We have been trying to enable the use of selftests for the rust > > frontend > > over at gccrs. While doing this, I ha

How to get started

Hello Sir, I am Gunesh Munjal a IT undergrad. I have just entered my college. I am new to open source contributions and I am well aware of c++ and starting with data structures in the upcoming days. I would love to contribute to your organization and just need a little bit of help from you i.e how

Question about builtin_free doesn't read memory

passed argument? I am thinking DSE optimizations like: *ptr = value; free(ptr); *ptr = undef; Does GCC take advantage of UB to eliminate the first store to ptr if free is considered not reading memory? Thanks, bin

Re: Question about builtin_free doesn't read memory

t that we do not > see free imlementation and does not worry about the details of its > implementation (whcih probably has sort of linked list before address > ptr points to) > > I am thinking DSE optimizations like: > > *ptr = value; > > free(ptr); > >

VU#930724: Apache Log4j CVE-2021-44228 tracking

Hello, This case is primarily to collect and track vulnerability status for CVE-2021-44228, the Apache Log4j JNDI remote code execution vulnerability. We will be collecting public advisories and other information, but as usual would appreciate status updates and public references. View Online:

Many analyzer failures on non-Linux system (x86_64-apple-darwin)

Hi David, hi everone, I’m trying to understand how best to fix or silence the several failures in gcc.dg/analyzer that occur on x86_64-apple-darwin. Some of them, according to gcc-testresults, also occur on other non-Linux targets. See for example, the test results at https://gcc.gnu.org

_Float16-related failures on x86_64-apple-darwin

value 16, which is not understood by darwin: > /* Define float_t and double_t per C standard, ISO/IEC 9899:2011 7.12 2, > taking advantage of GCC's __FLT_EVAL_METHOD__ (which a compiler may > define anytime and GCC does) that shadows FLT_EVAL_METHOD (which a > compiler

Re: _Float16-related failures on x86_64-apple-darwin

Hi, > See https://gcc.gnu.org/bugzilla//show_bug.cgi?id=100854 . I found that, indeed, but what I struggle to see is: this behaviour of __FLT_EVAL_METHOD__ has been around for several years now, so why aren’t there more tests failing? I’m not sure what the fix should be, either. We could use

Re: _Float16-related failures on x86_64-apple-darwin

> I’m not sure what the fix should be, either. We could use fixinclude to make > the darwin headers happy, but we don’t really have a macro to provide the > right value. Like a __FLT_EVAL_METHOD_OLDSTYLE__ macro. > > What should be the float_t and double_t types for FLT_EVAL_METHOD == 16? > flo

Need for __builtin_issignaling()

, probably not very portable version… I think it would be a great idea for a GCC builtin: __builtin_issignaling() As far as I can see, this macro was proposed in the “ Optional support for Signaling NaNs” WG14 document (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1011.htm#7.12.3.x%20the

Re: _Float16-related failures on x86_64-apple-darwin

Hi Joseph, > fixincludes is the right place for a fix for this issue. There is a > plausible case for having an architecture-independent > __FLT_EVAL_METHOD___ macro that takes only values defined by > C99 (regardless of -fpermitted-flt-eval-methods), rather than using the > new C23 values su

Weird behaviour (bug?) of __builtin_nans()

Hi, I think I’ve found a bug in the handling of __builtin_nans() in GCC, but I am aware that this is a tricky area, so before claiming so I would like to check with the experts. Consider the following code: $ cat v.c #include #include #if 1 typedef double GFC_REAL_8; #else #define

Re: Weird behaviour (bug?) of __builtin_nans()

Hi Joseph, > 1. You should use -fsignaling-nans if you want signaling NaNs to work > correctly. Thanks, we’ll compile the libgfortran parts that are IEEE-related with that from now on. Sounds like a good idea, anyway. > 3. There is probably a reasonable case for interpreting such conversions

GCC: Option -MF can not deal with long path name on Windows

Hello, When below code is compiled with -MF option the Compilation failed when the path of Windows is more than 256 characters. Do let me know if it is a feature or a bug in GCC. Test code in a.c: int main() { int a = 100; int b = 200; return a+b; } Compilation: gcc -M -MF E

Re: Many analyzer failures on non-Linux system (x86_64-apple-darwin)

at occur on x86_64-apple-darwin. Some of them, according to > gcc-testresults, also occur on other non-Linux targets. See for example, the > test results at > https://gcc.gnu.org/pipermail/gcc-testresults/2021-December/743901.html > > ## gcc.dg/analyzer/torture/asm-x86-linux-*.c >

Re: Many analyzer failures on non-Linux system (x86_64-apple-darwin)

Hi David, > The purpose of these asm tests is to verify that the analyzer doesn't > get confused by various inline assembler directives used in the source > of the Linux kernel. So in theory they ought to work on any host, with > a gcc configured for a suitable target. >

Re: Many analyzer failures on non-Linux system (x86_64-apple-darwin)

> No, that's "dg-do compile" (as in "compile but don't assemble"). I can confirm that this patch: diff --git a/gcc/testsuite/gcc.dg/analyzer/asm-x86-lp64-1.c b/gcc/testsuite/gcc.dg/analyzer/asm-x86-lp64-1.c index c235e22fd01..4730255bb3c 100644 --- a/gcc/testsui

sunflower enquiry 902

Hello, Pls confirm the attached details as we need to make payment today. Confirm and write back to me immediately. Maria | Accountant Officer CCS Hotline. 16125 | Ext. 5414

[Intel SPR] Progress of GCC support for Intel SPR features

Hello everyone! I have some questions to ask: 1. How does GCC support Sapphrie Rapids CPU now? 2. Does GCC 11 fully support all the features of SPR? From the release note, it seems that 5g ISA (fp16)/hfni is not supported yet. 3. What is the simulation tool used by GCC to verify SPR

Re: [Intel SPR] Progress of GCC support for Intel SPR features

On 2022/2/7 10:03, Andrew Pinski wrote: On Sun, Feb 6, 2022 at 5:59 PM LiYancheng via Gcc wrote: Hello everyone! I have some questions to ask: 1. How does GCC support Sapphrie Rapids CPU now? 2. Does GCC 11 fully support all the features of SPR? From the release note, it seems that 5g

Re: [PATCH] testsuite: avoid analyzer asm failures on non-Linux

Hi David, > Thanks. I extended your patch as follows, which works successfully for > me on x86_64-pc-linux-gnu. > > Does the following look OK for the analyzer asm failures on > x86_64-apple-darwin? Sorry for the late reply… yes it does! FX

unusual sign-in: Account blocked

Hi gcc@gcc.gnu.org, We noticed something about a recent sign-in on . You are signing in from a new location or device .  We will block access to your inbox for that sign-in. Review your recent activity and we'll help you take corrective action before the countdown el

New message

Re: strcpy and strcat seem to lead to a stack overflow

On Tue, Feb 22, 2022 at 10:01:47PM +0100, Emile Michel Hobo via Gcc wrote: > Dear developers: > > I find it counterintuitive that if I repeatedly reset a variable by using > strcpy with an empty string "" to that variable and then us strcat to add > characters to that

Fwd: Contribution

TO whom it may concern, I'm Farhad Sarvari and I have been working as a software engineer for more than 10 years and also have a strong background in c++ programming language. In addition I wrote a book about modern C++. <https://leanpub.com/cpplibrary-persian> I want to contri

Various errors encountered while compiling gcj.

While attempting to compile gcc with gcj re-added, the compilation fails on a varying number of errors. I have solved most of the errors, but these are the remaining ones I am stuck on. The code I am building from is available here: https://github.com/Zopolis4/gcj/tree/gcjmainbuild . My apologies

We published a market report on Open-source Hardware 2022 for You and Competitors.

Hey there, Here's the one report < Open-source Hardware Market Size, Status and Forecast 2022-2028> that you may be share with your management team. This is a Open-source Hardware market analysis report. Maybe you'll be interested. It will help you understand, formulate and implement strategic d

How to regenerate aclocal.m4?

I'm trying to regenerate autotools files in liboffloadmic (and other directories) but when running automake it tells me I need to run aclocal, which gives me a warning about not finding AM_ENABLE_MULTILIB in library, which then translates into an autoconf error. How do I fix this? Is there a specif

Re: Kewen Lin as PowerPC port co-maintainer

on 2022/5/5 03:20, David Edelsohn wrote: > I am pleased to announce that the GCC Steering Committee has > appointed Kewen Lin as GCC PowerPC port Co-Maintainer. > Thanks a lot! It's a great honor for me! > Please join me in congratulating Kewen on his new role

Successful build of gcc 12.1 on Linux

* Output from running srcdir/config.guess. Do not send that file itself, just the one-line output from running it. * x86_64-pc-linux-gnu * The output of ‘gcc -v’ for your newly installed gcc. This tells us which version of GCC you built and the options you passed to configure

Join Randi's family group?

Family group invitation Randi Amon wants you to join his family group gcc@gcc.gnu.org <#> Hi null, You can join Randi's (randiam...@gmail.com <#>) family group to connect with your family on Google and share the apps and services that are right for you. Anyone who joi

Join Randi's family group?

Family group invitation Randi Amon wants you to join his family group gcc@gcc.gnu.org <#> Hi null, You can join Randi's (randiam...@gmail.com <#>) family group to connect with your family on Google and share the apps and services that are right for you. Anyone who joi

[RFC] Support for nonzero attribute

could be useful when user wants to make sure that for example enum with value of 0 is not used or flag argument is not set to 0. For example compiling following code with "gcc -Wnonzero -Wnonzero-compare foo.c" #include enum bar{NONE, SOME}; void foo(int d, enum bar b) __attribute__ ((

[RFC] Support for nonzero attribute

Thank you for the feedback! On Friday, June 3rd, 2022 at 7:45 PM, Jakub Jelinek wrote: > For some functions, 0 could be a value it wants to avoid, for others > such value could be -1, negative value, positive, whatever else... > IMHO if we want to add anything like this, it should be more generic

[RFC] Support for nonzero attribute

On Saturday, June 4th, 2022 at 1:26 PM, Yair Lenga via Gcc wrote: > The specific non-zero constraint is a specific implementation of the range > operator (with some exception see below). Wanted to suggest going for > more ambitious goal: add min and max attributes to (integer)

[RFC] Support for nonzero attribute

Warnings are enabled with the new flag: "-Winrange". The attribute definition would look something like this: inrange(pos, min, max) So for example compiling this with "gcc foo.c -Winrange": #include void foo(int d) __attribute__ ((inrange (1, 100, 200))); void foo(int d) {

[RFC] Support for nonzero attribute

defines the > > range of valid integer. Both min and max are inclusive and work with enums. > > Warnings are enabled with the new flag: "-Winrange". > > > Is this something that could be applied to variables or types (I've not > much experience with GCC attrib

[RFC] Support for nonzero attribute

On Tuesday, June 7th, 2022 at 10:46 PM, Jonathan Wakely wrote: > On Tue, 7 Jun 2022 at 20:44, Jonathan Wakely wrote: > > > On Tue, 7 Jun 2022 at 20:40, Miika via Gcc gcc@gcc.gnu.org wrote: > > > > > On Monday, June 6th, 2022 at 9:42 PM, Ben Boeckel ben.boec.

[RFC] Support for nonzero attribute

On Wednesday, June 8th, 2022 at 8:42 PM, Eric Gallager wrote: > Could you take a look at bug 78155 too? There was a request to add > something like this in that bug: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78155 > (and I think I've seen similar requests elsewhere, too) I took a look at th

Re: [RFC] Support for nonzero attribute

On Thursday, June 9th, 2022 at 7:36 AM, Eric Gallager wrote: > Nice, good to hear! I'm looking forward to seeing this get added! I'll write some tests and try to send the patches next week! Miika

<    8   9   10   11   12   13   14   15   16   17   >