Bug 45587 - the processor(s) that read the .texi files mess up.
Summary: the processor(s) that read the .texi files mess up.
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: other (show other bugs)
Version: unknown
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-07 19:35 UTC by Kenneth Zadeck
Modified: 2010-09-07 20:43 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments
doc.patch (1.02 KB, patch)
2010-09-08 03:42 UTC, Kenneth Zadeck
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Kenneth Zadeck 2010-09-07 19:35:40 UTC
the lceil part of md.texi is:
======================
@cindex @code{lceil@var{m}@var{n}2}
@item @samp{lceil@var{m}2}
Convert operand 1 (valid for floating point mode @var{m}) to fixed
point mode @var{n} as a signed number rounding up and store in
operand 0 (which has mode @var{n}).
======================
which prints in both the info and in the html as:
======================
`lceilm2'
    Convert operand 1 (valid for floating point mode m) to fixed point mode n as a signed number rounding up and store in operand 0 (which has mode n).
======================
note that the @var{n} does not print in the name.  it should be `lceilmn2'
this appears to be a systematic failure, not just with this entry.  However, there are some where it comes out correctly, like lrintmn2.
Comment 1 jsm-csl@polyomino.org.uk 2010-09-07 19:54:37 UTC
Subject: Re:   New: the processor(s) that read the .texi
 files mess up.

On Tue, 7 Sep 2010, zadeck at naturalbridge dot com wrote:

> @cindex @code{lceil@var{m}@var{n}2}

This is the index entry, with "n".

> @item @samp{lceil@var{m}2}

This is the part for the main text of the manual, without "n".

> Convert operand 1 (valid for floating point mode @var{m}) to fixed
> point mode @var{n} as a signed number rounding up and store in
> operand 0 (which has mode @var{n}).
> ======================
> which prints in both the info and in the html as:
> ======================
> `lceilm2'
>     Convert operand 1 (valid for floating point mode m) to fixed point mode n
> as a signed number rounding up and store in operand 0 (which has mode n).
> ======================
> note that the @var{n} does not print in the name.  it should be `lceilmn2'

@var{n} isn't in the name for the main manual, just for the index entry.  
If you look in the index, you'll probably find the @var{n} there.  Fix 
whichever of the @item and the @cindex is wrong to agree with whichever is 
right.

Comment 2 Kenneth Zadeck 2010-09-07 20:31:00 UTC
Subject: Re:  the processor(s) that read the .texi files
 mess up.

thanks, i will fix the doc and commit.

On 09/07/2010 03:54 PM, joseph at codesourcery dot com wrote:
> ------- Comment #1 from joseph at codesourcery dot com  2010-09-07 19:54 -------
> Subject: Re:   New: the processor(s) that read the .texi
>  files mess up.
>
> On Tue, 7 Sep 2010, zadeck at naturalbridge dot com wrote:
>
>   
>> @cindex @code{lceil@var{m}@var{n}2}
>>     
> This is the index entry, with "n".
>
>   
>> @item @samp{lceil@var{m}2}
>>     
> This is the part for the main text of the manual, without "n".
>
>   
>> Convert operand 1 (valid for floating point mode @var{m}) to fixed
>> point mode @var{n} as a signed number rounding up and store in
>> operand 0 (which has mode @var{n}).
>> ======================
>> which prints in both the info and in the html as:
>> ======================
>> `lceilm2'
>>     Convert operand 1 (valid for floating point mode m) to fixed point mode n
>> as a signed number rounding up and store in operand 0 (which has mode n).
>> ======================
>> note that the @var{n} does not print in the name.  it should be `lceilmn2'
>>     
> @var{n} isn't in the name for the main manual, just for the index entry.  
> If you look in the index, you'll probably find the @var{n} there.  Fix 
> whichever of the @item and the @cindex is wrong to agree with whichever is 
> right.
>
>
>   
Comment 3 Kenneth Zadeck 2010-09-07 20:43:22 UTC
i am fixing the doc as joseph suggests, this is not a bug with the tool.
will commit after i look at the results.

Comment 4 zadeck@gcc.gnu.org 2010-09-08 03:38:54 UTC
Subject: Bug 45587

Author: zadeck
Date: Wed Sep  8 03:38:40 2010
New Revision: 163987

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163987
Log:
2010-09-08  Kenneth Zadeck <zadeck@naturalbridge.com>
	PR doc/45587
	* doc/md.texi: Fixed modes on several standard pattern names.


Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/doc/md.texi

Comment 5 Kenneth Zadeck 2010-09-08 03:42:21 UTC
Subject: Re:  the processor(s) that read the .texi files
 mess up.



On 09/07/2010 11:38 PM, zadeck at gcc dot gnu dot org wrote:
> ------- Comment #4 from zadeck at gcc dot gnu dot org  2010-09-08 03:38 -------
> Subject: Bug 45587
>
> Author: zadeck
> Date: Wed Sep  8 03:38:40 2010
> New Revision: 163987
>
> URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=163987
> Log:
> 2010-09-08  Kenneth Zadeck <zadeck@naturalbridge.com>
>         PR doc/45587
>         * doc/md.texi: Fixed modes on several standard pattern names.
>
>
> Modified:
>     trunk/gcc/ChangeLog
>     trunk/gcc/doc/md.texi
>
>
>   
Comment 6 Kenneth Zadeck 2010-09-08 03:42:21 UTC
Created attachment 21733 [details]
doc.patch