Localized write permission for OS maintainers
Hello, I have a question regarding the localized write permission for OS maintainers. In https://www.gnu.org/software/gcc/svnwrite.html we have "Localized write permission. This is for people who have primary responsibility for ports, front ends, or other specific aspects of the compiler. These folks are allowed to make changes to areas they maintain and related documentation, web pages, and test cases without approval from anyone else, and approve other people's changes in those areas. They must get approval for changes elsewhere in the compiler. Maintainers of a port maintain the relevant files in |gcc/config|, documentation, web pages, and test cases and aspects of these relevant to that port. Port maintainers do not have approval rights beyond this." Does this cover OS specific areas in the gcc/config.gcc file? For example: https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01214.html -- Sebastian Huber, embedded brains GmbH Address : Dornierstr. 4, D-82178 Puchheim, Germany Phone : +49 89 189 47 41-16 Fax : +49 89 189 47 41-09 E-Mail : sebastian.hu...@embedded-brains.de PGP : Public key available on request. Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
RE: Localized write permission for OS maintainers
> Does this cover OS specific areas in the gcc/config.gcc file? For > example: > > https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01214.html I can’t answer authoritatively but I would expect it does include OS specific areas of config files. However, as an arch port maintainer I would be wary of an OS maintainer tweaking something that is arch specific OS config. Hope that makes sense. Thanks, Matthew
affiliate
This is to request your assistance for a lucrative project in Asia. Kindly respond for specifics.
RE: Localized write permission for OS maintainers
On December 18, 2014 4:14:54 AM CST, Matthew Fortune wrote: >> Does this cover OS specific areas in the gcc/config.gcc file? For >> example: >> >> https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01214.html > >I can’t answer authoritatively but I would expect it does include >OS specific areas of config files. However, as an arch port maintainer >I would be wary of an OS maintainer tweaking something that is >arch specific OS config. Hope that makes sense. That's how it has worked for me in practice. But the RTEMS specific configurery is usually very similar to another CPU-elf and I generally ask for reviews to make sure it is the right thing to do. This also covers RTEMS specific runtime port files. >Thanks, >Matthew --joel (from a mobile device, forgive brevity and typos)
Re: GCC 4.8.4 Status Report (2014-12-05)
> Ok. Committed to the 4.8 branch as rev. 218873 FX
Re: bug in lra-constraints.c (simple_move_p register_move_cost)
On 2014-12-16 9:53 AM, BELBACHIR Selim wrote: Hi, I may have found a bug when I was trying to port my private backend to new LRA pass (using gcc 4.9.2+patches). In lra-constraints.c, in function simple_move_p, the target hook targetm.register_move_cost is called with two badly swapped parameters : targetm.register_move_cost (GET_MODE (src), sclass, dclass) should be : targetm.register_move_cost (GET_MODE (src), dclass, sclass) In my port of GCC it leads to an error when checking constrain_operands at the end of LRA pass Thanks for reporting this typo. I'll fix it soon. It did not affect other ports as usually the cost is symmetric relative to the args (especially when the cost is 2).
gcc-4.8-20141218 is now available
Snapshot gcc-4.8-20141218 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20141218/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_8-branch revision 218877 You'll find: gcc-4.8-20141218.tar.bz2 Complete GCC MD5=2c8a48fa69449a81fef5ef553009b9bf SHA1=cf6752e86d95beefece81cf23b8e8ec30f2254e6 Diffs from 4.8-20141211 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.8 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.
