Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-04-08 Thread Eldar Kusdavletov via Gcc
Thanks a lot, Andi! I’ve submitted the final version of the proposal on the GSoC platform. I really appreciate your feedback, as well as the input from everyone who took the time to review and help refine the idea. It made a significant difference. I hope for the opportunity to contribute to GCC

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-04-06 Thread Andi Kleen
On 2025-04-06 10:46, Eldar Kusdavletov wrote: Thanks, Andi — I’ve updated the proposal to reflect your feedback, especially around separating frontend and backend phases. I now describe the backend instrumentation as building on existing per-function timevars and focusing on trace formatting and

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-04-05 Thread Andi Kleen
On Mon, Mar 31, 2025 at 11:14:47PM +0300, Eldar Kusdavletov wrote: > I wanted to follow up on my previous email regarding my interest in > participating in Google Summer of Code with GCC. I saw the discussion in the > thread, but it seems there was no final confirmation. > > Could you please let m

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-04-04 Thread Andi Kleen
On Fri, Apr 04, 2025 at 07:21:47AM +0300, Eldar Kusdavletov wrote: > Thanks. I’ve submitted a more concrete version of the proposal — attaching it > here. > > I’ve taken a brief look at Clang’s implementation, but the idea isn’t to > follow > it exactly — rather, to provide a similar kind of trac

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-04-04 Thread waffl3x via Gcc
On Thursday, April 3rd, 2025 at 10:45 PM, Andi Kleen wrote: > > > On Fri, Apr 04, 2025 at 07:21:47AM +0300, Eldar Kusdavletov wrote: > > > Thanks. I’ve submitted a more concrete version of the proposal — attaching > > it > > here. > > > > I’ve taken a brief look at Clang’s implementation, b

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-03-31 Thread Eldar Kusdavletov via Gcc
I wanted to follow up on my previous email regarding my interest in participating in Google Summer of Code with GCC. I saw the discussion in the thread, but it seems there was no final confirmation. Could you please let me know if everything is in order and whether I can proceed with submitting my

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-03-26 Thread Sam James via Gcc
Jakub Jelinek via Gcc writes: > On Tue, Mar 25, 2025 at 07:21:32AM +0300, Eldar Kusdavletov via Gcc wrote: >> *Dear GCC Mentoring Team,* >> I am writing to submit my proposal for the Google Summer of Code (GSoC) >> 2025 program, aiming to contribute to the GCC project by implementing a >> feature

Re: [Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-03-26 Thread Jakub Jelinek via Gcc
On Tue, Mar 25, 2025 at 07:21:32AM +0300, Eldar Kusdavletov via Gcc wrote: > *Dear GCC Mentoring Team,* > I am writing to submit my proposal for the Google Summer of Code (GSoC) > 2025 program, aiming to contribute to the GCC project by implementing a > feature similar to Clang's -ftime-trace. This

[Draft] GSoC 2025 Proposal: Implementing Clang's -ftime-trace Feature in GCC

2025-03-24 Thread Eldar Kusdavletov via Gcc
*Dear GCC Mentoring Team,* I am writing to submit my proposal for the Google Summer of Code (GSoC) 2025 program, aiming to contribute to the GCC project by implementing a feature similar to Clang's -ftime-trace. This feature generates performance reports detailing the compiler's time distribution a