| Message ID | EA1BC3A8-E49D-4EAE-A8BF-6E13792711D1@sandoe.co.uk |
|---|---|
| State | New |
| Headers | show |
| Series | [pushed] doc : Fix build error from r11-4972. | expand |
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 4e5197fc038..4ddbf80a229 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -7429,8 +7429,7 @@ data in this way can reduce program startup times. This attribute is specific to ELF targets and relies on the linker to place such data in the right location -@item objc_nullability (@var{nullability kind}) @r{(Objective-C and Objective --C++ only)} +@item objc_nullability (@var{nullability kind}) @r{(Objective-C and Objective-C++ only)} @cindex @code{objc_nullability} variable attribute
(aonther re-send, no sign of the message on patches archive) Hi As reported on irc, some tex tools don’t like @r{} commands being split. For the record, I tried a number of things to wrap the line: 1/ putting the @r{} on the line after the @item that didn't work - the (Objective-C and Objective-C++ only) also appeared on the following line. 2/ splitting on the space following the ‘and', but that resulted in; (Objective-C andObjective-C++ only) regardless of whether I appended a space to the end of the first line or the start of the second. 3/ splitting as per the original patch worked OK for my installation (tex live 2019). .. if there’s a general solution to this, I’d be interested. suggested fix was to allow the long line, at least in the short term, pushed to master, Iain ---- Some tex tools don't allow the @r{} command to be split across lines. Fixed by making the change occupy a long line. gcc/ChangeLog: * doc/extend.texi: Don't try to line-wrap an @r command. --- gcc/doc/extend.texi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) This attribute applies to pointer variables only. It allows marking the pointer with one of four possible values describing the conditions under