groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: A file suffix for troff's output.


From: Alejandro Colomar
Subject: Re: A file suffix for troff's output.
Date: Mon, 10 Apr 2023 18:06:32 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1

Hi Ralph,

On 4/10/23 17:56, Ralph Corderoy wrote:
> Hi Alejandro,
> 
>> I'd use .cat.set for UTF8/ASCII pages, and .html.set for HTML pages.
> 
> Yes, I was thinking if a .tr was being turned into several formats then
> I'd include troff's -T device in the filename.
> 
> But as a general case, where just one -T is being targeted, a plain
> chapter.set seems sufficient.

Sure, .set should be good for most purposes.  It's just for my very
specific case that I use compound suffixes.  In my C projects, I do
similar things (and even more in C/C++ mixed projects), where you can
find the following suffixes (for each pair of .c/.h files):

$ find tmp/ | grep memzero | sort
tmp/c/mem/set/memzero.c
tmp/c/mem/set/memzero.c.O0.i
tmp/c/mem/set/memzero.c.O0.o
tmp/c/mem/set/memzero.c.O0.s
tmp/c/mem/set/memzero.c.O1.i
tmp/c/mem/set/memzero.c.O1.o
tmp/c/mem/set/memzero.c.O1.s
tmp/c/mem/set/memzero.c.O2.i
tmp/c/mem/set/memzero.c.O2.o
tmp/c/mem/set/memzero.c.O2.s
tmp/c/mem/set/memzero.c.O3.i
tmp/c/mem/set/memzero.c.O3.o
tmp/c/mem/set/memzero.c.O3.s
tmp/c/mem/set/memzero.c.Ofast.i
tmp/c/mem/set/memzero.c.Ofast.o
tmp/c/mem/set/memzero.c.Ofast.s
tmp/c/mem/set/memzero.c.Og.i
tmp/c/mem/set/memzero.c.Og.o
tmp/c/mem/set/memzero.c.Og.s
tmp/c/mem/set/memzero.c.Os.i
tmp/c/mem/set/memzero.c.Os.o
tmp/c/mem/set/memzero.c.Os.s
tmp/c/mem/set/memzero.c.d
tmp/c/mem/set/memzero.c.i
tmp/c/mem/set/memzero.c.lint-c.checkpatch.touch
tmp/c/mem/set/memzero.c.lint-c.clang-tidy.touch
tmp/c/mem/set/memzero.c.lint-c.cppcheck.touch
tmp/c/mem/set/memzero.c.lint-c.cpplint.touch
tmp/c/mem/set/memzero.c.lint-c.iwyu.touch
tmp/c/mem/set/memzero.c.o
tmp/c/mem/set/memzero.c.s
tmp/c/mem/set/memzero.h
tmp/c/mem/set/memzero.h.O0.gch
tmp/c/mem/set/memzero.h.O1.gch
tmp/c/mem/set/memzero.h.O2.gch
tmp/c/mem/set/memzero.h.O3.gch
tmp/c/mem/set/memzero.h.Ofast.gch
tmp/c/mem/set/memzero.h.Og.gch
tmp/c/mem/set/memzero.h.Os.gch
tmp/c/mem/set/memzero.h.d
tmp/c/mem/set/memzero.h.gch
tmp/c/mem/set/memzero.h.lint-c.checkpatch.touch
tmp/c/mem/set/memzero.h.lint-c.clang-tidy.touch
tmp/c/mem/set/memzero.h.lint-c.cppcheck.touch
tmp/c/mem/set/memzero.h.lint-c.cpplint.touch
tmp/c/mem/set/memzero.h.lint-c.iwyu.touch


This allows me to compare how each optimization level affects my code,
and learn the exact changes in assembler output easily.  As a nice side
effect of building with so many optimization levels, I get a higher
number of diagnostics about my code, since some optimizations enable
certain diagnostics, and others truncate them (due to the code being
removed at some point).

Cheers,
Alex

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]