Hi Kritika,
On Wed, Feb 22, 2023 at 6:49 AM Kritika Rag via Gcc wrote:
>
> Hello Everyone!
>
> I’m Kritika Rag, a Computer Science pre-final year undergraduate
> student from India. I’m quite passionate about web development and
> competitive programming and now I’m looking forward to contributin
.cppreference.com/w/cpp/header/type_traits
>
> Also, I would appreciate receiving the contact information for the
> project mentor, Patrick Palka.
>
> Sincerely,
> Ken Matsui
On Sun, Mar 3, 2019 at 5:16 PM Jeff Law wrote:
>
> On 3/3/19 4:06 PM, Patrick Palka wrote:
> > Hi everyone,
> >
> > I am very interested in working on GCC as part of GSoC this year. A few
> > years
> > ago I was a somewhat active code contributor[1] and unf
Hi Richard, Jakub and Martin,
First of all I'm sorry for the very late reply, and I will be more
punctual with my replies from now on.
On Fri, Mar 8, 2019 at 4:35 AM Richard Biener
wrote:
>
> On Thu, Mar 7, 2019 at 7:20 PM Martin Sebor wrote:
> >
> > On 3/4/19 6:17 AM, Richard Biener wrote:
> >
many as one can over the summer.
Would any of these ideas work as a GSoC project?
Regards,
Patrick Palka
[1]: https://gcc.gnu.org/git/?p=gcc.git;a=search;s=ppalka;st=author
[2]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72443#c2
[3]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74762#c7
[4]: ht
On Sat, Jul 16, 2016 at 4:27 AM, Andreas Schwab wrote:
> Andrew Pinski writes:
>
>> On Fri, Jul 15, 2016 at 6:46 PM, Patrick Palka wrote:
>>> The build step that invokes "ranlib libbackend.a" (which immediately
>>> follows the invocation of "ar rc l
The build step that invokes "ranlib libbackend.a" (which immediately
follows the invocation of "ar rc libbackend.a ...") takes over 7 seconds
on my machine and causes the entire 450MB archive to be rewritten. By
instead making the build system use ar rcs -- so that the archive and
its index are bu
On Mon, May 30, 2016 at 1:06 PM, Jakub Jelinek wrote:
> On Mon, May 30, 2016 at 01:01:09PM -0400, Patrick Palka wrote:
>> I'm sad that this discussion died so soon without Antonio's points
>> being adequately addressed.
>
> But how do you want to address that?
I'm sad that this discussion died so soon without Antonio's points
being adequately addressed.
GCC 6, compared to GCC 5, now emits an extra newline between error
messages. Is this intended?
$ cat error.c
int x = a;
int y = b;
$ gcc-5 error.c
error.c:1:9: error: ‘a’ undeclared here (not in a function)
int x = a;
^
error.c:2:9: error: ‘b’ undeclared here (not in a function)
int y
On Thu, Feb 20, 2014 at 1:14 PM, Jonathan Wakely wrote:
> On 20 February 2014 15:31, Patrick Palka wrote:
>> (I counted nearly 100 (non-debug)
>> functions that could be made static in gcc, and 4 in libstdc++, by the
>> way.)
>
> Which were the four in libstdc++?
>
On Thu, Feb 20, 2014 at 7:42 AM, Jonathan Wakely wrote:
> On 20 February 2014 10:02, Patrick Palka wrote:
>> On Thu, Feb 20, 2014 at 2:16 AM, Jonathan Wakely
>> wrote:
>>> On 13 February 2014 20:47, Patrick Palka wrote:
>>>> On a related note, would a patch
On Thu, Feb 20, 2014 at 2:16 AM, Jonathan Wakely wrote:
> On 13 February 2014 20:47, Patrick Palka wrote:
>> On a related note, would a patch to officially enable
>> -Wmissing-declarations in the build process be well regarded?
>
> What would be the advantage?
A missing decl
Hi everyone,
I noticed that the GCC build process currently only uses the
-Wmissing-prototypes flag, and not the -Wmissing-declarations flag.
It seems that the former flag only works on C source files, which
means that GCC's source files no longer benefit from this flag as they
are now C++ files.
14 matches
Mail list logo
