Bug 111288 - formatting mistake in HTML documentation
Summary: formatting mistake in HTML documentation
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: other (show other bugs)
Version: 13.2.0
: P3 normal
Target Milestone: 14.0
Assignee: Not yet assigned to anyone
URL:
Keywords: documentation
Depends on:
Blocks:
 
Reported: 2023-09-04 20:49 UTC by Bruno Haible
Modified: 2023-12-04 17:24 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed: 2023-09-06 00:00:00


Attachments
proposed fix (670 bytes, application/mbox)
2023-09-04 20:49 UTC, Bruno Haible
Details
Rendering before applying the fix (186.94 KB, image/png)
2023-09-04 20:50 UTC, Bruno Haible
Details
Rendering after applying the fix (187.54 KB, image/png)
2023-09-04 20:50 UTC, Bruno Haible
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Haible 2023-09-04 20:49:01 UTC
Created attachment 55839 [details]
proposed fix

In https://gcc.gnu.org/onlinedocs/gcc/Integer-Overflow-Builtins.html the declarations of the last 6 functions are not well formatted: the highlighted token is "int" or "long", not the name of the built-in.

The attached patch fixes it. I'm also attaching the rendering before and after the patch is applied.
Comment 1 Bruno Haible 2023-09-04 20:50:00 UTC
Created attachment 55840 [details]
Rendering before applying the fix
Comment 2 Bruno Haible 2023-09-04 20:50:19 UTC
Created attachment 55841 [details]
Rendering after applying the fix
Comment 3 Andrew Pinski 2023-09-04 20:50:54 UTC
patches should be posted to gcc-patches@ after reading https://gcc.gnu.org/contribute.html
Comment 4 Bruno Haible 2023-09-04 21:04:54 UTC
My proposed patch is a correction to commit 2b4e0415ad664cdb3ce87d1f7eee5ca26911a05b by Jakub Jelinek.

> patches should be posted to gcc-patches@ after reading https://gcc.gnu.org/contribute.html

I do have a copyright assigment for GCC in place. But I don't have time to follow the entire procedure. Maybe someone else can take over, from this point?
Comment 5 Jonathan Wakely 2023-09-06 13:41:13 UTC
If you have an assignment in place then all you need to do is send the patch to the gcc-patches list.
Comment 6 Bruno Haible 2023-12-04 10:22:58 UTC
A fix that includes my patch has been applied by Jakub Jelinek on 2023-12-01:
https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=ff99671ac3ea583a9d65c8c3cd3ff4aad1d68592

This bug report is therefore FIXED.