On 01/19/2018 03:09 PM, 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.
Hi. If I'm correct time spent for programming is May 14, 2018 - August 6, 2018. Let me briefly describe the topics: 2a) A Type Sanitizer Both LLVM and GCC compilers do share a common sanitizer library called libsanitizer. The library has recently received support of typed-based sanitization (TySan). Goal of the task would be to investigate and prototype usage of type-based aliasing rules information, provided by GCC. As a result the information can be leverage to detect violations of strict aliasing rules. Student can start with analysis of differences of aliasing analysis in between the GCC and LLVM compiler. 2c) Textual Representation of LTO Object Files Link-Time Optimization (LTO) is a technique where an intermediate representation of translation units is serialized and loaded during link time. That leads to massive optimization opportunities as a compiler can see the whole program. Current format of LTO object file is binary and we would welcome to have also an equivalent textual representation. The format should be human readable and easily adjustable. Such improvement would help a lot to reproduce and debug complication LTO bugs that require multiple object files to be compiled. Martin > >> 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. > > Martin >
