From: "Sławomir Lach" <slawek@lach.art.pl>
To: gcc@gcc.gnu.org
Subject: Re: Learning hardware optimization patch
Date: Tue, 15 Nov 2022 19:44:45 +0100 [thread overview]
Message-ID: <2680919.mvXUDI8C0e@localhost.localdomain> (raw)
In-Reply-To: <5902985.lOV4Wx5bFT@localhost.localdomain>
Dnia wtorek, 15 listopada 2022 19:42:13 CET Sławomir Lach pisze:
> I am wonder if this will be good choice to allow gcc to generate AI data
> about best optimization approach on user computer.
>
> Yes. GCC team will provide source code for some examples and (once low
> hardware consumption) made gcc to compile these sources with various
> optimization patch. It will take avg run time of each patch. Of course - it
> will run compilation once there is many free resources on computer.
>
Not patch, but path - sorry. Applying different patch, which have optimization
is bad idea, because it forces developer to carry out many path :-D .
> Why? To allow user select --best-optimiation-speed-for-my-machine or another
> optimization criteria, which will depends on AI data sheet.
>
> What do you think?
>
> Another idea is to allow adding feature point to program. Program will
> report that user is using some feature. In next step, linker could made
> optimization based on this - by simply, compiles only functionality, which
> is used by user. Rest functions will be put into shared objects and special
> code to load this shared object could been injected to executable.
>
> I am not very good in programming, but have had crazy ideas about lot of
> stuff.
>
> Best regards,
> Lach Sławomir.
prev parent reply other threads:[~2022-11-15 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 18:42 Sławomir Lach
2022-11-15 18:44 ` Sławomir Lach [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2680919.mvXUDI8C0e@localhost.localdomain \
--to=slawek@lach.art.pl \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).