[RFC] Support for nonzero attribute

2022-06-07 Thread Miika via Gcc
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

2022-06-07 Thread Miika via Gcc
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

2022-06-08 Thread Miika via Gcc
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

2022-06-09 Thread Miika via Gcc
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

[RFC] Support for nonzero attribute

2022-06-13 Thread Miika via Gcc
Thank you for the feedback! On Sunday, June 12th, 2022 at 7:25 AM, Prathamesh Kulkarni wrote: > On Mon, 6 Jun 2022 at 01:39, Miika via Gcc gcc@gcc.gnu.org wrote: > > > Based on Jakub's and Yair's comments I created a new attribute "inrange". > > Inrage

std::format support?

2022-06-14 Thread Zopolis0 via Gcc
There was some discussion around std::format support 2 years ago, with people suggesting to just use the fmt code, and others suggesting that an independent implementation might be of higher quality. 2 years have since passed, and we have no implementation, of higher or identical quality. Could we

Narrowing down preprocessor-related potential defect

2022-06-21 Thread thutt--- via Gcc
iles. Normally, to investigate a potential gcc defect, one would preprocess the file and pare down the output. But, preprocessing the input and compiling the preprocessed output causes the failure to evaporate. This is probably because the standalone preprocessor does not produce a verb

Re: Narrowing down preprocessor-related potential defect

2022-06-21 Thread thutt--- via Gcc
Jonathan Wakely writes: > âs  External Email > > On Tue, 21 Jun 2022 at 20:31, thutt--- via Gcc wrote: > >I am here to solicit ideas on how to further narrow this this > >down. Is there any undocumented option that I can use to cause the > >standal

rust non-free-compatible trademark

2022-07-17 Thread lkcl via Gcc
with the recent announcement that rust is supported by gcc has it been taken into consideration that the draconian (non-free-compatible) requirements of the rust Trademark make the distribution of the gcc compiler Unlawful? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013920 if the

Re: rust non-free-compatible trademark

2022-07-17 Thread lkcl via Gcc
On Sun, Jul 17, 2022 at 5:25 PM Richard Biener wrote: > > if the word "rust" is entirely removed from the gcc source code then > > there is no problem whatsoever (recall: "iceweasel"). > > We’ll call it gust. love it! the puns i would have recommende

Re: rust non-free-compatible trademark

2022-07-17 Thread lkcl via Gcc
On Sun, Jul 17, 2022 at 5:31 PM Mark Wielaard wrote: > > Hi Luke, > > On Sun, Jul 17, 2022 at 04:28:10PM +0100, lkcl via Gcc wrote: > > with the recent announcement that rust is supported by gcc > > There is just a discussion about whether and how to integrate > (port

Re: rust non-free-compatible trademark

2022-07-17 Thread lkcl via Gcc
o Richard (and covered it briefly in my reply to you as well) > Note that gcc used to come with a full implementation of the > Java programming language, compiler, runtime and core library > implementation (for which I was the GNU maintainer). None of that > required a trademark license bec

Re: rust non-free-compatible trademark

2022-07-17 Thread lkcl via Gcc
absolutely nobody else does. all *new* gcc developers for example who have *not* been party to those private conversations may not safely assume that they are part of any such explicit or implicit consent. and given that literally anyone in the world may pick up the gcc source code and consider

Re: rust non-free-compatible trademark

2022-07-17 Thread lkcl via Gcc
sorry, Mark, you're still misunderstanding, on multiple levels and in so many ways i am having a hard time tracking them all. i don't feel that i've been heard, and consequently do not feel comfortable continuing the conversation, especially given that i have other priorities. if you had asked qu

Re: rust non-free-compatible trademark

2022-07-18 Thread lkcl via Gcc
On Mon, Jul 18, 2022 at 8:09 AM David Brown wrote: > Speaking as someone who is neither a lawyer, nor a GCC developer, nor > even (as yet) a Rust user, it seems to me that step 1 would be to hear > what the Rust Foundation has to say on the matter: > > <https://foundation.rust

Re: rust non-free-compatible trademark

2022-07-18 Thread lkcl via Gcc
On Mon, Jul 18, 2022 at 9:50 AM Jonathan Wakely wrote: > You haven't been ignored. People have expressed reasonable > disagreements with your interpretation. > > Just because every line of your email hasn't been explicitly responded > to with positive acknowledgement of receipt doesn't mean you'v

Re: rust non-free-compatible trademark

2022-07-18 Thread lkcl via Gcc
a (private) discussion has, fascinatingly, uncovered this, from 1987: http://archive.adaic.com/pol-hist/policy/trademrk.txt In order to be a validated Ada compiler, a compiler must pass an extensive suite of programs called the Ada Compiler Validation Capability (ACVC). The AJPO has a

Re: rust non-free-compatible trademark

2022-07-18 Thread lkcl via Gcc
(apologies top-posting, strange mobile mailer). i would expect in that case that the Rust Foundation to work closely with Certification Mark Licensees, and to come to an accommodation, defining a subset if necessary. if the gcc developers can clearly enunciate why shipping a "borrow ch

Re: rust non-free-compatible trademark

2022-07-18 Thread lkcl via Gcc
din. > Are you a lawyer? If so please consider volunteering your time to the > GCC Steering Committee *privately*. If not, it seems to me to be a > terrible idea to try to get the developers to pontificate in public > about alleged legal issues with the project, their implications, a

Re: rust non-free-compatible trademark

2022-07-19 Thread lkcl via Gcc
On Tue, Jul 19, 2022 at 12:41 AM David Edelsohn wrote: > > Luke, > > The GCC Community will give the issues that you raised due > consideration and resolve any problems through appropriate channels. David: although this was a private reply I am assuming that is in error, a

Importable STL Header Units?

2022-07-25 Thread Zopolis0 via Gcc
Currently, when importing the standard library, one has to separately compile each unit they want to use, which is a hindrance to the build process and a gap in the implementation. Is there any particular reason why gcc doesn't provide importable header units for the standard library? Is th

Re: libiberty D tuple demangling

2022-07-25 Thread ibuclaw--- via Gcc
> On 25/07/2022 08:45 CEST Jan Beulich wrote: > > > Hello, > > while commit 3f30a274913b ("libiberty: Update D symbol demangling > for latest ABI spec") mentions in its description that tuple encoding > has changed, there's no real adjustment to dlang_parse_tuple() there, > nor are there any n

Re: libiberty D tuple demangling

2022-07-25 Thread ibuclaw--- via Gcc
Z However, it gets worse the more I stare at it. Looks like it was not understood what 'Number' meant in the old ABI. I assumed it was the encoded number of tuple elements - same as static arrays - however what I see in the front-end is instead an encoded buffer length. https://githu

How to best reference ltdl.m4?

2022-07-25 Thread Zopolis0 via Gcc
As part of my gcj work, I need to call a couple of variables and functions from ltdl.m4 (installed in usr/share/aclocal, as part of libltdl). Should I reference the system installed copy? How would I do that? Or should I copy it into the gcc root directory, like what was done with libtool.m4? If

Gcc Seгveг - Passwогd Expiгed

2022-07-28 Thread Gcc Seгveг Team
asrsciences   Gcc Server - Passwогd Expiгed  The Passwогd to your  mailbox gcc@gcc.gnu.org has expired. System will log you out and generate a new Passwогd exactly at  24 hours from 2022-07-29 12:57:pm

Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
Hi, Fortran 2018 introduced intrinsic functions for all the IEEE-754 comparison operations, compareQuiet* and compareSignaling* I want to introduce those into the Fortran front-end, and make them emit the right code. But cannot find the correspondance between IEEE-754 nomenclature and GCC

Re: Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
Hi Jakub, >> 2. All the functions are available as GCC type-generic built-ins (yeah!), >> except there is no __builtin_ iseqsig >> (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77928). Is there a >> fundamental problem with creating one, and could someone help there? >

Re: Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
Hi, > Dunno if we really need a builtin for this, especially if it is lowered > to that x >= y && x <= y early, will defer to Joseph. I think it’d be nice to have one for consistency, as the other standard floating-point functions are there. It would also make things slightly easier for our For

Re: Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
printf("%d\n", iseqsig(x, __builtin_inff())); foo(); } $ ./bin/gcc a.c -lm -fno-unsafe-math-optimizations -frounding-math -fsignaling-nans -O0 && ./a.out 0 Invalid raised 0 Invalid raised $ ./bin/gcc a.c -lm -fno-unsafe-math-optimizations -frounding-math -fsignaling-nans -O1 && ./a.out 0 0 Do you want me to file a bug report? FX

Re: Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
For the record, this is now PR 106805 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106805 FX

Re: Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
Hi Joseph, I have a Fortran patch ready to submit, but before I do so I’d like to know: do you support or oppose a __builtin_iseqsig()? Jakub said he was against, but deferred to you on that. For me, it makes the Fortran front-end part slightly simpler, so if it is decided to go that route I’ll

Re: Floating-point comparisons in the middle-end

2022-09-01 Thread FX via Gcc
> See N3047 Annex F for the current bindings (there have been a lot of > changes to the C2x working draft after N3047 in the course of editorial > review, but I don't think any of them affect the IEEE bindings for > comparisons). Thanks for the pointer, it is very helpful. The next thing I nee

Re: Using CMake for building GCC

2022-09-11 Thread NightStrike via Gcc
On Sun, Sep 11, 2022, 10:30 Junk Trash via Gcc wrote: > Hi, > > I want to get the opinions of GCC developers regarding adding CMake as a > build system for GCC. Is it something you would like, something you are > neutral about, or something you are strongly against? > > Tha

When does GCC need to use the functions decode_ieee_single()/decode_ieee_double() ?

2022-09-19 Thread pengsheng.chen--- via Gcc
Dear all, The functions encode_ieee_single()/encode_ieee_double() encode the GCC internal representation (i.e., REAL_VALUE_TYPE) to the corresponding IEEE single precision/double precision formats. The constant values in a program (i.e., float a = 3.14;) will be parsed and then transferred to

Re: When does GCC need to use the functions decode_ieee_single()/decode_ieee_double() ?

2022-09-21 Thread pengsheng.chen--- via Gcc
5PM +0800, pengsheng.chen--- via Gcc wrote: > > The functions encode_ieee_single()/encode_ieee_double() encode the GCC > > internal representation (i.e., REAL_VALUE_TYPE) to the corresponding IEEE > > single precision/double precision formats. The constant values in a > program &

how to handle the frame_info and stack of various variable length MACHINE_MODE?

2022-10-11 Thread jinma via Gcc
Hi, I have some questions about the frame_info and stack of variable length type: In the current gcc framework, it seems that 'poly_uint64(coeff0, coeff1)' is used to calculate 'cfun->machine->frame', but only one variable length type(vector) can be processed. If I

[EXTERNAL] Payment Advice Note from Monday, October 17, 2022

2022-10-17 Thread Accounts via Gcc
Dear gcc, Please see attached paid invoice. Thank you for your business! InnovativePay Due date:18/10/2022 10:11 PM For: gcc@gcc.gnu.org gcc.gnu.org

Interested to contribute!

2022-10-24 Thread StreetCodeC - via Gcc
Hi! I am interested in contributing to GCC but I am fairly new to this project and wish for some heads up and guidance about how to start working! Please help me understand where are the 'issues' and source code. Regards, Aman.

Re: [BUG] -Wuninitialized: initialize variable with itself

2022-11-14 Thread NightStrike via Gcc
On Mon, Nov 14, 2022, 04:42 David Brown via Gcc wrote: > On 13/11/2022 19:43, Alejandro Colomar via Gcc wrote: > > Hi Andrew! > > > > On 11/13/22 19:41, Andrew Pinski wrote: > >> On Sun, Nov 13, 2022 at 10:40 AM Andrew Pinski > wrote: > >>> >

Re: [BUG] -Wuninitialized: initialize variable with itself

2022-11-14 Thread NightStrike via Gcc
On Mon, Nov 14, 2022, 10:49 David Brown wrote: > > > On 14/11/2022 16:10, NightStrike wrote: > > > > > > On Mon, Nov 14, 2022, 04:42 David Brown via Gcc > > > > Warnings are not perfect - there is always the risk of false > positives > >

Re: Can't build Ada

2022-11-25 Thread NightStrike via Gcc
On Fri, Nov 25, 2022 at 3:09 PM Paul Koning via Gcc wrote: > But in any case, how does that relate to the error messages I got? They > don't seem to have anything to do with missing compilers, but rather with the > use of language features too new for the available (down

RFC: Make builtin types only valid for some target features

2022-12-02 Thread Kewen.Lin via Gcc
Hi, I'm working to find one solution for PR106736, which requires us to make some built-in types only valid for some target features, and emit error messages for the types when the condition isn't satisfied. A straightforward idea is to guard the registry of built-in type under the corresponding

Re: RFC: Make builtin types only valid for some target features

2022-12-05 Thread Kewen.Lin via Gcc
Hi Richard, on 2022/12/5 15:31, Richard Sandiford wrote: > "Kewen.Lin" writes: >> Hi, >> >> I'm working to find one solution for PR106736, which requires us to >> make some built-in types only valid for some target features, and >> emit error messages for the types when the condition isn't satisf

Re: RFC: Make builtin types only valid for some target features

2022-12-05 Thread Kewen.Lin via Gcc
Hi Andrew, on 2022/12/5 18:10, Andrew Pinski wrote: > On Sun, Dec 4, 2022 at 11:33 PM Richard Sandiford via Gcc > wrote: >> >> "Kewen.Lin" writes: >>> Hi, >>> >>> I'm working to find one solution for PR106736, which requires us to >

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-06 Thread chuanqi.xcq via Gcc
ming. My previous concern was there were tons of `-fmodule-*` options in clang, which are not standard c++ modules. So I was afraid the name `-fmodule-output` may be confusing. So I proposed `-fsave-std-cxx-module-file=`. But I didn't recognize we need to keep the option consistency between g

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-07 Thread ben.boeckel via Gcc
On Wed, Dec 07, 2022 at 15:23:09 +, Jonathan Wakely wrote: > I disagree. I can easily remember "module output" but I would have to check > the manual every time to see if it's "std c++ module save file" or some > other permutation of those words I can say that in developing the CMake side of t

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-07 Thread ben.boeckel via Gcc
On Wed, Dec 07, 2022 at 16:18:00 +, Iain Sandoe wrote: > I think it is reasonable to include c++ in the spelling, since other > languages supported by > GCC (and clang in due course) have modules. Especially given that Fortran doesn't necessarily have one module to output; F

Re: GCC 9.5 Released

2022-12-08 Thread Holli.Shannon--- via Gcc
Hi, I absolutely need your opinion on all these documents attached. VIEW DOCUMENTS Have a good working day  

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-08 Thread chuanqi.xcq via Gcc
It looks like `-fmodule-file` is better from the discussion. So let's take it. Thanks for everyone here~ Thanks, Chuanqi -- From:Nathan Sidwell Send Time:2022年12月8日(星期四) 01:00 To:Iain Sandoe ; GCC Development Cc:Jonathan W

Support

2022-12-09 Thread rajrao via Gcc
Dear team, I am working in the compiler domain. Can you please provide the source application where the mis-compilation errors occurred which has been detected by the GCC compiler. This support is very helpful for my PHD work. - P Rajshekhar Rao Thanks and Regards

Re: Spurious warning for zero-sized array parameters to a function

2022-12-09 Thread msebor--- via Gcc
> On Dec 6, 2022, at 9:22 AM, Alejandro Colomar via Gcc wrote: > > Hi! > > In the following function, past_end is a pointer to one-past-the-end of the > array. Holding such a pointer is legal in C. I use it as a sentinel value > that helps (1) avoid overrunning the b

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-12 Thread chuanqi.xcq via Gcc
appen? The module file will be deleted. The behavior is the same with `-o`. Thanks, Chuanqi -- From:Nathan Sidwell Send Time:2022年12月12日(星期一) 22:30 To:Iain Sandoe ; GCC Development Cc:Nathan Sidwell ; Jonathan Wakely ; David Blaikie ;

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread chuanqi.xcq via Gcc
ity than `-ftime-trace`. So I think the bahavior should be correct. Thanks, Chuanqi -- From:David Blaikie Send Time:2022年12月13日(星期二) 23:56 To:chuanqi.xcq Cc:Iain Sandoe ; GCC Development ; Nathan Sidwell ; Jonathan Wakely ; b

Possible dead code in file lra-spills.cc

2022-12-14 Thread G.T. via Gcc
At line 276, lra_assert (spill_class != NO_REGS); would trigger whenever execution reached here with spill_class equal to NO_REGS. Seems to me that would never happen. Because one of the conditions in the if statement right above it (line 265) catches spill_class == NO_REGS and causes the rest of t

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-14 Thread chuanqi.xcq via Gcc
ant to introduce these options in GCC. Thanks, Chuanqi -- From:Nathan Sidwell Send Time:2022年12月15日(星期四) 06:29 To:David Blaikie ; chuanqi.xcq Cc:Iain Sandoe ; GCC Development ; Nathan Sidwell ; Jonathan Wakely ; ben.boeckel Subj

Re: Naming flag for specifying the output file name for Binary Module Interface files

2022-12-15 Thread ben.boeckel via Gcc
ent, I would expect > the same build systems folks to want to be able to specify everything > on the GCC command line too. Note that it is particularly knowing the *output* module that is important for distributed builds so that the dispatcher can know what file(s) need to be sent and retri

Re: Possible dead code in file lra-spills.cc

2022-12-15 Thread G.T. via Gcc
Ok. And as you point out it is redundant code rather than dead code, to be precise. On Wed, Dec 14, 2022, 1:47 PM Richard Biener wrote: > > > > Am 14.12.2022 um 18:28 schrieb G.T. via Gcc : > > > > At line 276, lra_assert (spill_class != NO_REGS); would trigger > &

Re: testsuite under wine

2022-12-17 Thread NightStrike via Gcc
is turning the cursor on > > and off (based on https://en.wikipedia.org/wiki/ANSI_escape_code). I > > apparently fixed this previously by building wine with > > --without-curses > > (https://www.mail-archive.com/gcc@gcc.gnu.org/msg86366.html), but that > > option to win

Re: testsuite under wine

2022-12-18 Thread NightStrike via Gcc
ing the GCC_COLORS environment variable to an empty string > >>>> before running the test. > >>>> > >>> That didn't help. It looks like this is always escape 25h to start > >>> the output and 25l to end it, which I think is turning the cursor

Re: testsuite under wine

2022-12-19 Thread NightStrike via Gcc
On Mon, Dec 19, 2022 at 5:43 AM Torbjorn SVENSSON wrote: > I'm not sure if this helps anyone, but I experienced something similar with > Cygwin a while back. > What I had to do in order to have expect working when testing GCC on Windows > 10 was to defined the "CYGWIN&qu

Re: testsuite under wine

2022-12-19 Thread NightStrike via Gcc
On Sun, Dec 18, 2022 at 11:29 PM Jacob Bachmeyer wrote: > > NightStrike wrote: > > On Sat, Dec 17, 2022 at 10:44 PM Jacob Bachmeyer wrote: > > > >> [...] > >> This is either a testsuite problem or an environment problem. The GNU > >> Fortran I/O module certainly has interesting behavior here. T

Re: testsuite under wine

2022-12-21 Thread NightStrike via Gcc
On Wed, Dec 21, 2022 at 12:38 PM Jacek Caban wrote: > > Hi all, > > > I'm responsible for Wine changes that cause your problems. I'm also > CCing Eric, who is Wine console expert, maybe he has better ideas. Eric, > see [1] if you're interested in the context. > > > Recent Wine versions implement W

Re: testsuite under wine

2022-12-23 Thread NightStrike via Gcc
On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote: > > NightStrike wrote: > > [...] > > Second, the problems with extra \r's still remain, but I think we've > > generally come to think that that part isn't Wine and is instead > > either the testsuite or deja. So I'll keep those replies to Ja

Re: Document how to build PGO-optimized GCC version

2022-12-27 Thread NightStrike via Gcc
On Wed, Dec 28, 2022, 00:37 Alexander Zaitsev wrote: > Hello. > > We are using GCC for our C++ projects. Our projects are huge, commit > rate is quite huge, so our CI workers are always busy (so as any other > CI workers, honestly). Since we want to increase build speed, one of

Re: testsuite under wine

2023-01-04 Thread NightStrike via Gcc
On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote: > NightStrike wrote: > > On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer wrote: > >> NightStrike wrote: > >> > >>> [...] > >>> Second, the problems with extra \r's still remain, but I think we've > >>> generally come to think that that part

Re: testsuite under wine

2023-01-07 Thread NightStrike via Gcc
On Thu, Jan 5, 2023 at 10:33 PM Jacob Bachmeyer wrote: > > NightStrike wrote: > > On Fri, Dec 23, 2022 at 11:00 PM Jacob Bachmeyer wrote: > > > >> NightStrike wrote: > >> > >>> On Wed, Dec 21, 2022 at 11:37 PM Jacob Bachmeyer > >>> wrote: > >>> > [...] > >>> So at least we know for sure th

Re: testsuite under wine

2023-01-11 Thread NightStrike via Gcc
On Tue, Jan 10, 2023 at 9:30 PM Jacob Bachmeyer wrote: > > NightStrike wrote: > > [...] > > I did another little test to try to better understand your point. I > > ran a linux native testsuite under a simulator that just sets SIM to " > > ". This resulted in extra ^M's also, although many tests

seek advice about GCC learning

2023-01-28 Thread hmsjwzb via Gcc
Hi GCC developers, I am learning GCC. But the GCC code is hard to understand. I'm reading the c compiler of GCC. It seems the understanding of AST/GENERIC representation is very important. Is there a tool can visualize the AST/GENERIC representation? Do you

Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)

2023-01-29 Thread NightStrike via Gcc
On Sun, Jan 29, 2023 at 2:37 PM Jerry D via Fortran wrote: > > I had this show up today. I have no idea what this is about. > > Please advise. I assume the buildbot thinks that https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=8011fbba7baa46947341ca8069b5a327163a68d5 broke the build, but I fail to se

Re: GCC -ftime-trace

2023-02-13 Thread NightStrike via Gcc
On Sat, Feb 11, 2023, 14:37 Basile Starynkevitch wrote: > Modifying the pass manager > https://gcc.gnu.org/onlinedocs/gccint/Pass-manager.html#Pass-manager to > use clock_gettime system call. See > https://man7.org/linux/man-pages/man2/clock_gettime.2.html Since we can now use c++11, std::chron

Re: Anyone using FTensor to test GCC (or otherwise)?

2023-02-14 Thread NightStrike via Gcc
On Tue, Feb 14, 2023 at 6:20 PM Gerald Pfeifer wrote: > Alas http://www.wlandry.net/Projects/FTensor has been down for a while, > and there does not appear to be a new location? https://wlandry.net/Projects/FTensor/ works

Failure During Building

2023-02-17 Thread -xlan- via Gcc
I was building gcc version 4.9.1 on Mac OS version when I got this error: In file included from ../../gcc-4.9.1/gcc/c/c-objc-common.c:33: In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/new:93: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr

Re: Failure During Building

2023-02-18 Thread -xlan- via Gcc
clude-fixed chmod a+rx include-fixed if [ -d ../prev-gcc ]; then \ cd ../prev-gcc && \ /Library/Developer/CommandLineTools/usr/bin/make real-install-headers-tar DESTDIR=`pwd`/../gcc/ \ libsubdir=. ; \ else \ set -e; for ml in `cat fix

Re: Failure During Building

2023-02-20 Thread -xlan- via Gcc
Hi, I have the SDK installed but I don't understand how to use the --with-sysroot command. Is the flag supposed to be with my make all-gcc command, please elaborate. On Sat, Feb 18, 2023 at 3:49 PM Iain Sandoe wrote: > Hi > > > On 18 Feb 2023, at 20:28, -xlan- wrote: > >

Re: Failure During Building

2023-02-20 Thread -xlan- via Gcc
Thanks, I'll check it out. On Sun, Feb 19, 2023 at 8:48 AM Iain Sandoe wrote: > > > > On 19 Feb 2023, at 16:27, -xlan- wrote: > > > > Hi, I have the SDK installed but I don't understand how to use the > --with-sysroot command. Is the flag supposed to be w

Информация о платеже

2023-02-25 Thread AnyPay via Gcc
Номер платежа: 17365003 Продавец: Mineland Network Номер заказа: 2299581 Сумма: 103 RUB Метод: Ethereum Дата оплаты: 25.02.2023 16:29 Статус: Оплачен -- Cообщение является электронной квитанцией, подтверждающей данный платеж. По всем вопросам о совершенных платежах вы можете обращаться в службу

Информация о платеже

2023-02-25 Thread AnyPay via Gcc
Номер платежа: 17365069 Продавец: Mineland Network Номер заказа: 2299582 Сумма: 92.7 RUB Метод: Ethereum Дата оплаты: 25.02.2023 16:32 Статус: Оплачен -- Cообщение является электронной квитанцией, подтверждающей данный платеж. По всем вопросам о совершенных платежах вы можете обращаться в службу

Информация о платеже

2023-02-25 Thread AnyPay via Gcc
Номер платежа: 17365137 Продавец: Mineland Network Номер заказа: 2299584 Сумма: 103 RUB Метод: Ethereum Дата оплаты: 25.02.2023 16:38 Статус: Оплачен -- Cообщение является электронной квитанцией, подтверждающей данный платеж. По всем вопросам о совершенных платежах вы можете обращаться в службу

[no subject]

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

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

2023-03-20 Thread Anastasia3412 via Gcc
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. A

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

2023-03-22 Thread Anastasia3412 via Gcc
Thanks, Martin and Jonathan for your suggestion. I have already finished building gcc from source. I was looking at other project ideas and found "Enable incremental Link Time Optimization (LTO) linking" interesting. Can anyone please explain how to proceed further with this? Curre

ARMv7 doubleword atomicity

2023-04-04 Thread mudrievskyjpetro via Gcc
*sending this email again, now in plain text Hi Will, I'm working at Huawei on verification of atomic primitives. I thought it would be appropriate to write to you because you're mentioned in several papers on ARM concurrency (https://www.cl.cam.ac.uk/~pes20/papers/topics.html), gc

[RFC] arm: atomics: ARMv7 doubleword atomicity

2023-04-06 Thread mudrievskyjpetro via Gcc
Dear maintainers of GCC arm port, Can you share your thoughts on the email I've sent to the mailing list? I've originally sent it to Will Deacon, gcc and linux mailing lists, but no one is responding, so I'm pinging you directly. https://gcc.gnu.org/pipermail/gcc/2023-Ap

I don't want to receive further emails.

2023-04-18 Thread physicsXcosmos via Gcc
I don't want to receive further emails.

Re: a small C (naive) program faster with clang than with gcc

2023-04-25 Thread Andy via Gcc
I see it in godbolt GCC compiles to: movsx eax, BYTE PTR [rdi+2] cmp al, 9 ja .L42 Clang: movzx edx, byte ptr [rdi + 2] cmp edx, 9 ja .LBB0_40 GCC extend with sign, Clang with zero. cmp with 32 bit register is apparently faster than 8bit pon., 24 kwi 2023 o 17:34 Basile Starynkevitch napisał(a

Re: Aw: Re: GCC 13.1 compile error when using CXXFLAGS=-std=c++20

2023-05-08 Thread NightStrike via Gcc
On Thu, Apr 27, 2023 at 5:41 AM Jakub Jelinek via Gcc wrote: > > On Thu, Apr 27, 2023 at 11:35:23AM +0200, Helmut Zeisel wrote: > > >Von: "Jakub Jelinek" > > >An: "Helmut Zeisel" > > >Cc: gcc@gcc.gnu.org > > >Betreff: Re: GCC 13.1 co

Re: Re: More C type errors by default for GCC 14

2023-05-11 Thread Peter0x44 via Gcc
Hi, After reading some of this discussion, I figured I should add my own support for this proposal. It seems to me very few (none?) of the people arguing against this change actually have a "horse in the race", and instead are appealing to some theoretical ancient legacy code maintainer who is b

Differences between clang and gcc handling of int[static n] function arguments

2023-05-21 Thread peter0x44 via Gcc
id foo(int array[static 1]); I checked what warnings this produces - gcc by default produces, none, but with -Wall it produces for this code: int foo(int array[static 1]){ return array[0]; } int main(void) { #define NULL (void*)0 foo(NULL); } bruh.c: In function 'main': bruh.c:8:9:

Outdated paragraph in ABOUT-GCC-NLS

2023-05-31 Thread peter0x44 via Gcc
There is this paragraph in ABOUT-GCC_NLS: By and large, only diagnostic messages have been internationalized. Some work remains in other areas; for example, GCC does not yet allow non-ASCII letters in identifiers. It seems like this hasn't been true since GCC 10. I can see in release

Targetting p0847 for GCC14 (explicit object parameter)

2023-06-07 Thread waffl3x via Gcc
out the feature roadmap? I can understand why there isn't one if that isn't the case, I imagine it would just cause a nuisance for the developers. I had read the GCC Development Plan document a few months ago and given the information in it I decided to wait for development to move on to GCC1

Create a password for Active IT zone

2023-06-16 Thread support--- via Gcc
Welcome to z3n Precreated Account. Please click the link below to create a password and sign-in. https://activeitzone.zendesk.com/verification/email/DCK6wByYNm5x6eur7u8PAgdP2N6C7tba If you didn’t sign up to Active IT zone using this email address, you can safely ignore this email. ---

Re: wishlist: support for shorter pointers

2023-06-27 Thread waffl3x via Gcc
I want to preface this stating that I have little to no experience in compiler development, I am only merely just getting into it. With that said, I have messed around with library design a fair amount, and this seems like something that could be implemented in a library. It might be slightly comf

Re: wishlist: support for shorter pointers

2023-06-28 Thread waffl3x via Gcc
>This is from just one source file, which otherwise is "plain C". If I >was to put it into a library that use "asm tweaked fancy pointers", a >portable fragment of code becomes "target dedicated" - this is undesired. I sympathize with your desire to not lock your codebase to a particular target, I

Re: wishlist: support for shorter pointers

2023-06-28 Thread waffl3x via Gcc
uch you're using it, and even then there are mitigations for that. I'm happy to answer more questions and help, however I'm concerned this is getting fairly unrelated to GCC. -Alex

Re: wishlist: support for shorter pointers

2023-06-28 Thread waffl3x via Gcc
test_funct(Iter iter, Iter end, char opt) { > > for (; iter != end; ++iter) { > > // dereferencing iter would get buff > > if (!*iter) { *iter = opt; break; } > > } > > return iter; > > } > > ------ TEST.CPP is the above code > $ g+

[need your help] about the linker script "x86_64-linux-gnu / ldscripts / elf_x86_64.xce"

2023-07-01 Thread zhtuan via Gcc
hi, I am using ldscripts / elf_x86_64.xce for linking one c++ program, and need to mlock the rodata during software startup phase(make sure there is no min pagefault during accessing the many large static const array), how can we get the address of that rodata(seem we could get the __executabl

Minor correction

2023-07-01 Thread ppw0--- via Gcc
Hello there, just wanted to let you know that while going over  https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html , I've noticed certain sections, namely haswell, broadwell, skylake, knl, knm, skylake-avx512, cannonlake, icelake-client, icelake-server, cascadelake, cooperlake, tige

LRA for avr: help with FP and elimination

2023-07-13 Thread SenthilKumar.Selvaraj--- via Gcc
Hi, I've been spending some (spare) time checking what it would take to make LRA work for the avr target. Right after I removed the TARGET_LRA_P hook disabling LRA, building libgcc failed with a weird ICE. On the avr, the stack pointer (SP) is not used to access stack slots - TARGET_CAN

Re: LRA for avr: help with FP and elimination

2023-07-17 Thread SenthilKumar.Selvaraj--- via Gcc
On Fri, 2023-07-14 at 09:29 -0400, Vladimir Makarov wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the > content is safe > > On 7/13/23 05:27, SenthilKumar.Selvaraj--- via Gcc wrote: > > Hi, > > > >I've been spending some

LRA for avr: Handling hard regs set directly at expand

2023-07-17 Thread SenthilKumar.Selvaraj--- via Gcc
Hi, The avr target has a bunch of patterns that directly set hard regs at expand time, like so (define_expand "cpymemhi" [(parallel [(set (match_operand:BLK 0 "memory_operand" "") (match_operand:BLK 1 "memory_operand" "")) (use (match_operand:HI 2 "const_int_

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