| Message ID | CAMDjE1NZZP59YZn9+fCp=znZp5yVQo6U8ttDjMi-c=tW7JVOvQ@mail.gmail.com |
|---|---|
| State | New |
| Headers | show |
On Tue, Sep 17, 2013 at 10:35:22AM +0200, Nicklas Bo Jensen wrote: > Hi, > > Let me suggest to remove the section "Macros to control conditional > execution" in GCC internals. I assume the section is obsolete given > that it is empty. > > Best, > Nicklas > > 2013-09-17 Nicklas Bo Jensen <nbjensen@gmail.com> > * doc/tm.texi (Macros to control conditional execution): Hasn't this been already removed by http://gcc.gnu.org/ml/gcc-patches/2013-09/msg01231.html ? Marek
> Hasn't this been already removed by > http://gcc.gnu.org/ml/gcc-patches/2013-09/msg01231.html > ? Yes. Okay. Please ignore then. Best, Nicklas
Index: gcc/doc/tm.texi =================================================================== --- gcc/doc/tm.texi (revision 202626) +++ gcc/doc/tm.texi (working copy) @@ -6106,15 +6106,6 @@ returns @code{VOIDmode}. @end deftypefn -@node Cond Exec Macros -@subsection Macros to control conditional execution -@findex conditional execution -@findex predication - -There is one macro that may need to be defined for targets -supporting conditional execution, independent of how they -represent conditional branches. - @node Costs @section Describing Relative Costs of Operations @cindex costs of instructions
Hi, Let me suggest to remove the section "Macros to control conditional execution" in GCC internals. I assume the section is obsolete given that it is empty. Best, Nicklas 2013-09-17 Nicklas Bo Jensen <nbjensen@gmail.com> * doc/tm.texi (Macros to control conditional execution): Remove empty section. ---------- Forwarded message ---------- From: Andreas Schwab <schwab@linux-m68k.org> Date: Mon, Sep 16, 2013 at 8:03 PM Subject: Re: GCC internals conditional execution macro? To: Nicklas Bo Jensen <nbjensen@gmail.com> Cc: gcc@gcc.gnu.org Nicklas Bo Jensen <nbjensen@gmail.com> writes: > In GCC internals for GCC 4.8.1 and trunk the section "Macros to > control conditional execution" mentions that there exists a macro, but > does not name the macro? Which macro is thought of here? The macro has been removed in r188983 without removing the now empty section. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."