On Mon, Jun 7, 2021 at 10:35 AM Martin Liška wrote:
>
> On 6/7/21 8:14 AM, Richard Biener wrote:
> > Hmm, what's the problem with parsing the strings? The newlines are
> > only because of our line length limits and hard-coding them looks both
> > error-prone and ugly.
>
> For the future Sphinx co
On 6/7/21 8:14 AM, Richard Biener wrote:
Hmm, what's the problem with parsing the strings? The newlines are
only because of our line length limits and hard-coding them looks both
error-prone and ugly.
For the future Sphinx conversion, I need to replace content of the hook
definitions
in .def
On Sun, Jun 6, 2021 at 7:13 PM Martin Liška wrote:
>
> Hello.
>
> I'll need to parse output of tm.texi when converted to Sphinx for the future
> conversion. So that I split DEFHOOK documentation entries with newlines.
>
> I'll install the patch if there are no comments?
Hmm, what's the problem wi
Hello.
I'll need to parse output of tm.texi when converted to Sphinx for the future
conversion. So that I split DEFHOOK documentation entries with newlines.
I'll install the patch if there are no comments?
Thanks,
Martin
gcc/c-family/ChangeLog:
* c-target.def: Split long lines and repl