Re: Request for better syntax checking in lang.opt
Hi Martin, I was able to write a sanity check for these kind of issues, but it does not resolve all similar issues for other keywords. It's not easy to do it. Having looked at the origina awk code, I agree. Maybe, in the long term, a lex/yacc grammar with a monolithic C program to write out the headers wold be more suitable. Having said that, I think what you did is already quite valuable and will save some gcc developers from a few prmature grey hairs :-) So, I would recommend to commit as is. Sanity checks do not have to be perfect. Thanks for taking this on! Regards Thomas
bounty available for porting AVR backend to MODE_CC
Hi All, I don't subscribe but wanted developers to know there is a bounty available for porting the gcc AVR backend to use MODE_CC. Here is the reference: https://www.bountysource.com/issues/84630749-avr-convert-the-backend-to-mode_cc-so-it-can-be-kept-in-future-releases And this is a reference to the discussion on avrfreaks.net: https://www.avrfreaks.net/forum/avr-gcc-and-avr-g-are-deprecated-now Matt
Re: GCC 8.4 Status Report (2020-02-17)
Den 17-02-2020 kl. 12:45, skrev Jakub Jelinek: Status == It has been almost a year since GCC 8.3 has been released and GCC 8.4 release should have been released already, so we should concentrate on getting it out soon. Unfortunately we have two P1s, one of them is waiting for reporter's input, so we might as well just ignore it unless the input is provided, but the other, C++ FE one, looks something that should be fixed. If we get rid of the P1s, I'd like to create 8.4-rc1 on Wednesday, Feb 26th and release 8.4 the week afterwards. If you have any queued backports, please commit them to 8 branch (and 9 branch too, we'd like to release 9.3 soon too). Quality Data Priority # Change from last report --- --- P12 + 2 P2 284 + 75 P3 38 + 4 P4 151 - 11 P5 22 - 2 --- --- Total P1-P3 324 + 81 Total 497 + 68 Previous Report === https://gcc.gnu.org/ml/gcc/2019-02/msg00122.html Can this one be backported to gcc 8.4: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521 It fixes errors like: https://travis-ci.org/akien-mga/godot/jobs/654085724 ./core/math/vector3.h:40:8: note: candidate: 'constexpr Vector3::Vector3(Vector3&&)' editor/plugins/path_editor_plugin.cpp:214:176: error: call of overloaded 'Vector3(const Variant&)' is ambiguous The same code builds ok with gcc-7 and gcc-9 And the fix is confirmed with that fix backported on top of gcc-8-20200221 -- Thomas
Re: GCC 8.4 Status Report (2020-02-17)
On Sun, Feb 23, 2020 at 08:25:32PM +0200, Thomas Backlund wrote: > Can this one be backported to gcc 8.4: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86521 > > It fixes errors like: > https://travis-ci.org/akien-mga/godot/jobs/654085724 > > ./core/math/vector3.h:40:8: note: candidate: 'constexpr > Vector3::Vector3(Vector3&&)' > > editor/plugins/path_editor_plugin.cpp:214:176: error: call of overloaded > 'Vector3(const Variant&)' is ambiguous > > > The same code builds ok with gcc-7 and gcc-9 > > And the fix is confirmed with that fix backported on top of gcc-8-20200221 I'll defer that to Jason, it depends on whether the benefits of the backport outweight the risks and whether it had any follow-ups that would need to be backported too. Jakub
gcc-10-20200223 is now available
Snapshot gcc-10-20200223 is now available on https://gcc.gnu.org/pub/gcc/snapshots/10-20200223/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch master revision 3133bed5d0327e8a9cd0a601b7ecdb9de4fc825d You'll find: gcc-10-20200223.tar.xz Complete GCC SHA256=0815e475f95d0855dae1f7819007d753a4ad715a9799cd8db6c9f3205cd380c1 SHA1=84ab64dfb92866d1272f89c39b42c05010f8ce33 Diffs from 10-20200216 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-10 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
