Re: Tags out of gcc
On 5 October 2014 03:39, Adrian May wrote: > But it absolutely has to follow the preprocessor, so how do I do that? > I'm a bit surprised about that being a problem cos when I look at > preprocessor output it looks very convenient - I get one big file but > it's full of clues as to where it all came from. Perhaps I have to > hook those clues. Precisely. The information is there. The only open question is how to pass it to your plugin. See libcpp/macro.c and libcpp/include/cpplib.h and look for "callback". Then check init_c_lex in c-family/c-lex.c to see how the C/C++ FE uses them. Now you have to figure out which plugin hook your plugin should handle in order to take control of the callbacks before they are used. If nothing is early enough, you would need to add a new hook. (At least, this is what I would try first, perhaps there is even a better way). Cheers, Manuel.
GCC needs YOU!
Dear GCC users, As you may have noticed, GCC diagnostics have steadily improved in recent releases. In addition to the myriad of bugs fixed per release, every release had at least one major improvement in diagnostics. Unfortunately, the number of people contributing to this effort is very limited and we are more and more busy with other obligations. We need new blood and we need help. It has never been easier to contribute to GCC than nowadays. There are many ways you can help and there are tasks for every level of skill and time commitment. Some examples are: * There are 610 open bugs with the diagnostic keyword (https://gcc.gnu.org/bugzilla/buglist.cgi?keywords=diagnostic&limit=0&list_id=99232&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_format=advanced&resolution=---) Many are easy to implement and there is a description of the strategy available (https://gcc.gnu.org/PR49859, https://gcc.gnu.org/PR19808, https://gcc.gnu.org/PR48956, https://gcc.gnu.org/PR59717,https://gcc.gnu.org/PR43113 https://gcc.gnu.org/PR38612 https://gcc.gnu.orgPR17896 https://gcc.gnu.org/PR49973 https://gcc.gnu.org/PR53920 and many more like those) Many of them require further analysis. That means run GCC under GDB and figure out what went wrong. Just doing that would be extremely helpful. Other bigger projects are not technically difficult, just longer than a few hours: * Replace libiberty with gnulib. See http://gcc.gnu.org/ml/gcc-patches/2012-08/msg00362.html * Add a "spell-checker" (https://gcc.gnu.org/ml/gcc/2010-04/msg00104.html) https://gcc.gnu.org/PR52959 https://gcc.gnu.org/PR52277 * Investigate the open bugs in the macro unwinder (https://gcc.gnu.org/PR52998 https://gcc.gnu.org/PR55252 https://gcc.gnu.org/PR45333 https://gcc.gnu.org/PR60014) * C++ preprocessor ignores #pragma GCC diagnostic https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431 If you are into Fortran, it would be extremely helpful to contribute to fix this one: * https://gcc.gnu.org/PR54687 which is not only easy and incremental but consists mostly in deleting code and testing. Of course, if you are brave and a real hacker, you can always tackle some of the heavy stuff that no GCC hacker has figured out how to fix yet: * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 (and basically anything mentioned here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639) * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60090 * And any of the points here: https://gcc.gnu.org/wiki/Better_Diagnostics We need your help to make GCC better and keep it relevant! Thanks, Manuel.
Re: GCC needs YOU!
gcc Became very bad gcc Became the slower and more errors Because WeChange Implementation to c++ I hope to return to c Implementation 2014-10-05 12:10 جرينتش-07:00, Manuel López-Ibáñez : > Dear GCC users, > > As you may have noticed, GCC diagnostics have steadily improved in > recent releases. In addition to the myriad of bugs fixed per release, > every release had at least one major improvement in diagnostics. > > Unfortunately, the number of people contributing to this effort is > very limited and we are more and more busy with other obligations. We > need new blood and we need help. It has never been easier to > contribute to GCC than nowadays. There are many ways you can help and > there are tasks for every level of skill and time commitment. > > Some examples are: > > * There are 610 open bugs with the diagnostic keyword > (https://gcc.gnu.org/bugzilla/buglist.cgi?keywords=diagnostic&limit=0&list_id=99232&order=bug_status%2Cpriority%2Cassigned_to%2Cbug_id&query_format=advanced&resolution=---) > > Many are easy to implement and there is a description of the strategy > available (https://gcc.gnu.org/PR49859, https://gcc.gnu.org/PR19808, > https://gcc.gnu.org/PR48956, > https://gcc.gnu.org/PR59717,https://gcc.gnu.org/PR43113 > https://gcc.gnu.org/PR38612 https://gcc.gnu.orgPR17896 > https://gcc.gnu.org/PR49973 https://gcc.gnu.org/PR53920 and many more > like those) > > Many of them require further analysis. That means run GCC under GDB > and figure out what went wrong. Just doing that would be extremely > helpful. > > Other bigger projects are not technically difficult, just longer than > a few hours: > > * Replace libiberty with gnulib. See > http://gcc.gnu.org/ml/gcc-patches/2012-08/msg00362.html > > * Add a "spell-checker" (https://gcc.gnu.org/ml/gcc/2010-04/msg00104.html) > https://gcc.gnu.org/PR52959 https://gcc.gnu.org/PR52277 > > * Investigate the open bugs in the macro unwinder > (https://gcc.gnu.org/PR52998 https://gcc.gnu.org/PR55252 > https://gcc.gnu.org/PR45333 https://gcc.gnu.org/PR60014) > > * C++ preprocessor ignores #pragma GCC diagnostic > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53431 > > If you are into Fortran, it would be extremely helpful to contribute > to fix this one: > > * https://gcc.gnu.org/PR54687 which is not only easy and incremental > but consists mostly in deleting code and testing. > > Of course, if you are brave and a real hacker, you can always tackle > some of the heavy stuff that no GCC hacker has figured out how to fix > yet: > > * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=18501 (and basically > anything mentioned here: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639) > > * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60090 > > * And any of the points here: https://gcc.gnu.org/wiki/Better_Diagnostics > > We need your help to make GCC better and keep it relevant! > > Thanks, > > Manuel. > -- Think not of them, thou hast thy music too
Re: GCC needs YOU!
On 5 October 2014 20:29, Ali Abdul Ghani wrote: > gcc Became very bad Unsubstantiated nonsense that has nothing to do with the thread you're replying to. > gcc Became the slower and more errors If you have evidence for this please report it to bugzilla with code to reproduce the problem.
gcc-5-20141005 is now available
Snapshot gcc-5-20141005 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/5-20141005/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 5 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 215908 You'll find: gcc-5-20141005.tar.bz2 Complete GCC MD5=176fc335e0b54d0cfc9a62618d3e75ce SHA1=59816c86f500d8b715ad11e225aa557c7cd14c00 Diffs from 5-20140928 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-5 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.
