Hello,
Im sorry for posting to wrong group. Wasnt sure.
Let me try to explain more clearly. Please forgive my nonnative english.
My idea is something like ideally single gcc.exe would be built deployed
distributed runtests against per version per some/all frontends. We could
think as of whether m
On Thu, Mar 25, 2021 at 12:06:08PM +, Jonathan Wakely via Gcc wrote:
> What would be the benefit?
>
> I can understand the advantage of a single binary that is a
> cross-compiler for different targets (but it would be a huge task to
> get GCC there). You wouldn't need multiple complete copies
On Thu, 25 Mar 2021 at 09:43, pawel k. via Gcc-help
wrote:
>
> Hello,
> Not sure which list is right. I have ideas for code improvement for gcc.
Please don't cross-post to gcc@ and gcc-help@, there are almost no
topics relevant to both. You're discussing GCC development, so gcc@ is
the right plac
Hello,
Not sure which list is right. I have ideas for code improvement for gcc.
Idea1 langhooks cleanup
It basically involves clean up of lang hooks. Closing it in special class.
Might help to clean up massive defines etc spurious langhooks declarations
amongst others and removing some hooks from
