On Tue, 14 Apr 2020, Rasmus Villemoes wrote: > On 06/04/2020 23.18, Joseph Myers wrote: > > On Sat, 4 Apr 2020, Rasmus Villemoes wrote: > > > >> +#ifndef OUTFILES_SPEC > >> +#define OUTFILES_SPEC "%o" > >> +#endif > > > > A new target macro needs to be documented in tm.texi.in, > > Will do. > > > with tm.texi then being regenerated. > > Please include information on how I would go about doing that, or point > at a README/wiki that explains it. Is it just copying the generated > tm.texi from the build/gcc/ dir back to the src/gcc/doc/ dir?
Yes, copy from the build directory to the source directory. > Also, does my write-after-approval permission still apply after ~1.5 > years of non-activity, and the switch to git? If so, do I just make sure It's not time-limited. (However, when someone's employer changes they may need to get a new employer assignment / disclaimer before continuing to contribute changes that are significant for copyright purposes.) > my changes (after approval, of course) apply cleanly on top of master > and then push that? Yes, once changes are approved you should push them. -- Joseph S. Myers jos...@codesourcery.com
