public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Martin Jambor <mjambor@suse.cz>, gcc@gcc.gnu.org
Cc: Jakub Jelinek <jakub@redhat.com>,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	David Edelsohn <dje.gcc@gmail.com>,
	David Malcolm <dmalcolm@redhat.com>
Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
Date: Mon, 22 Jan 2018 15:10:00 -0000	[thread overview]
Message-ID: <a1a1d405-52f7-fd21-5304-e1666d8467d7@suse.cz> (raw)
In-Reply-To: <ri6vafyuebd.fsf@suse.cz>

On 01/19/2018 03:13 PM, Martin Jambor wrote:
> On Fri, Jan 19 2018, Martin Jambor wrote:
>> Hi,
>>
>> On Thu, Jan 18 2018, Martin Liška wrote:
>>> On 01/17/2018 06:54 PM, Martin Jambor wrote:
>>>
>> ...
>>>>
>>>> 2) Martin Liška is willing to mentor either:
>>>>    2a) -fsanitize=type (He provided URL https://reviews.llvm.org/D32197
>>>>        but it gives me a 404 error) or its prototype, or
>>>>    2b) bash code completion like:
>>>>        http://blog.llvm.org/2017/09/clang-bash-better-auto-completion-is.html
>>>>        but frankly I am afraid it is too small to be a GSoC project, or
>>>>    2c) textual representation of LTO stream a.k.a. lto-dump tool
>>>
>>> If there's an interest, I can specify in more detail these topics.
>>
>> First, we'll need (just) enough info to make the idea attractive for
>> students.  Then they will need to write a project proposal with
>> milestones and stuff
>> (https://google.github.io/gsocguides/student/writing-a-proposal).  I am
>> not sure how involved we will be at that point, but perhaps it is a good
>> idea to think about milestones anyway.
>>
>>> Note that
>>> David Malcolm is also interested in 2b) and he's willing to be co-mentor.
>>> The topic 2b) can be enlarged to an overhaul of option handling, with possible
>>> rewritten of current AWK scripts.
>>
>> I am still a bit sceptical about the b option.  IIRC there was an
>> objection on the IRC that rewriting AWK scripts would require extensive
>> testing in a wide variety of often obscure environments.  That may make
>> it ill-suited for GSoC.  But well... I am not strictly against it, but
>> we may need to set the expectations accordingly ...which may not make it
>> attractive neither for students not for Google.
>>
> 
> Ah no, I confused myself.  That was Joseph's issue with the idea of
> replacing libiberty with gnulib.  The problem with this one was getting
> a consensus to move away from AWK to python which would introduce a new
> dependency of the gcc project.  Someone experienced (and determined)
> from the community would have to drive that decision, we may not expect
> a newcomer, let a alone a student, to do it.

Here I can probably trigger the discussion about the transition from AWK
to another programming language. It's expected that it will take some time.
That said, do we still want to list the project as candidate for GSoC?

Martin

> 
> Sorry for the confusion,
> 
> Martin
> 

  reply	other threads:[~2018-01-22 15:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 17:54 Martin Jambor
2018-01-17 21:06 ` Joseph Myers
2018-01-19 13:17   ` Martin Jambor
2018-01-19 16:34     ` Joseph Myers
2018-01-19 17:31       ` Richard Biener
2018-01-17 22:16 ` Joel Sherrill
2018-01-18  9:19   ` Martin Liška
2018-01-19 13:50   ` Martin Jambor
2018-01-18  9:41 ` Martin Liška
2018-01-19 14:09   ` Martin Jambor
2018-01-19 14:13     ` Martin Jambor
2018-01-22 15:10       ` Martin Liška [this message]
2018-01-22 15:40     ` Martin Liška
2018-01-18 19:51 ` Eric Gallager
2018-01-18 20:31   ` Joseph Myers
2018-01-19 14:17     ` Martin Jambor
2018-01-18 23:10 ` Andi Kleen
2018-01-19 14:24   ` Martin Jambor
2018-01-23 10:56 ` Martin Jambor
2018-01-23 11:08   ` Prathamesh Kulkarni
2018-01-23 15:49     ` Martin Liška
2018-01-23 23:11     ` Martin Jambor
2018-02-13 13:02 ` Martin Jambor
2018-02-14 22:10   ` Janus Weil
2018-02-15  9:20     ` Martin Jambor
2018-02-15 10:52   ` Christopher Dimech
2018-02-15 12:12     ` Janus Weil
2018-02-15 13:59       ` Martin Jambor
2018-03-29 15:37   ` Joseph Myers
2018-03-29 16:40     ` Joseph Myers
2018-03-29 17:07     ` Martin Jambor
2018-04-03 11:30       ` Peryt, Sebastian
2018-04-03 14:09         ` Martin Jambor

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=a1a1d405-52f7-fd21-5304-e1666d8467d7@suse.cz \
    --to=mliska@suse.cz \
    --cc=dje.gcc@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=mjambor@suse.cz \
    /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).