From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14351 invoked by alias); 19 Sep 2002 13:03:58 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 14341 invoked from network); 19 Sep 2002 13:03:56 -0000 Received: from unknown (HELO is.elta.co.il) (199.203.121.2) by sources.redhat.com with SMTP; 19 Sep 2002 13:03:56 -0000 Received: from is (is [199.203.121.2]) by is.elta.co.il (8.9.3/8.8.8) with SMTP id PAA02781; Thu, 19 Sep 2002 15:01:06 +0200 (IST) Date: Thu, 19 Sep 2002 06:03:00 -0000 From: Eli Zaretskii X-Sender: eliz@is To: Andrew Cagney cc: gdb-patches@sources.redhat.com Subject: Re: [rfa:doco] document frame_align() In-Reply-To: <3D88A8BB.2010007@ges.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-09/txt/msg00470.txt.bz2 On Wed, 18 Sep 2002, Andrew Cagney wrote: > This documents the frame_align() architecture method. It also clarifies > the behavior of stack_align(). > > ok? Yes. However: Unlike @ref{STACK_ALIGN}, this function always adjusts the address Please don't use this technique. It sounds cute at first glance, but produces text in the Info version which looks awkwardly: Unlike *note STACK_ALIGN, this function always adjusts the address Instead, do it more straightforwardly: Unlike @code{STACK_ALIGN} (@pxref{STACK_ALIGN}), ... (In this particular case, the @pxref is actually redundant, since you have a @pxref like that a few lines before that.)