Hi, I was planning to include this in my final report, but it turned out
big enough as a rant to send it separately.
About my patch at [1], since I was using strnlen() in one of my dwarf2out
patches I had to also make sure configure tested for its availability, and
also provide it in libiberty
This year's GSOC has come to an end.
In a very brief summary, I achieved a few things this summer: Ported
patches from last year - some made it to mainline, extended old patches
and resubmitted them, wrote new but mostly small clean-ups/speed-ups. In a
nutshell:
[DF] Generate REFs in REGNO o
Hello,
I've finished some final updates, according to recommendations you
proposed. Please let me know what you think.
On Wed, 4 Jul 2012, Dimitrios Apostolou wrote:
On Thu, 28 Jun 2012, Dimitrios Apostolou wrote:
http://teras-ics.mooo.com:8003/
* 4 tests are now benchmarked: em
ase builds (e.g. lto/profiledbootstrap).
Thanks,
Dimitris
On Wed, 11 Jul 2012, Dimitrios Apostolou wrote:
Hello list,
we discussed the subject in the BOF but I didn't quite get what the consensus
is, so that I can start changing things.
What I have in mind is to introduce and document a new &q
On Mon, 2012-07-16 at 19:23 +0100, Jonathan Wakely wrote:
> Add @gcc.gnu.org to it?
Unfortunately this is rarely in agreement with MAINTAINERS. For now I
found it easier to just grep the Changelog file.
Thanks,
Dimitris
On Tue, 2012-07-17 at 11:24 +0200, Richard Guenther wrote:
> Note that people that patched a file are not necessary maintainers of that
> file.
> Maintainers are listed exclusively in the MAINTAINERS file.
I was just looking for a quick and easy hack for my own convenience,
based on the logic tha
Hello,
I'm trying to write a small script that shows emails addresses for all
committers of last year, for all files a patch touches. In the commit logs
however all committers are referred to by username, and grepping the
MAINTAINERS files sometimes doesn't bring up any email address (e.g. gre
Hello list,
we discussed the subject in the BOF but I didn't quite get what the
consensus is, so that I can start changing things.
What I have in mind is to introduce and document a new "make release"
target that builds GCC in the fastest /stable/ way possible, for example
--enable-checking=
On Tue, 10 Jul 2012, Dimitrios Apostolou wrote:
* Have a field in the bugzilla keeping "related ML threads" URLs. What I do
now is post a separate comment saying "discussed here" or "posted patch
here". Not sure if good enough, but on bugs I've not seen it i
Hi hp, thanks for the notes, I'm just going to highlight my point of view.
Regarding patch pinging, my take is that is should be seldom necessary,
for example I tend to forget my small patches after sometime. So IMHO
anyone replying anything is good, especially if he CCs the maintainer
(Dodji-
On Mon, 8 Jul 2012, gccad...@gcc.gnu.org wrote:
Snapshot gcc-4.8-20120708 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20120708/
Any idea who's responsible for this massive decrease in memory usage? :-)
Valgrind's massif isn't really helping me to track this one. See the
"mem
Hello,
On Thu, 28 Jun 2012, Dimitrios Apostolou wrote:
http://teras-ics.mooo.com:8003/
I've updated the page with some more measurements, please let me know what
you think.
The primary issue I've not been able to resolve is with function name
demangling: Valgrind uses l
On Sun, 1 Jul 2012, Sergei Trofimovich wrote:
* Unfortunately Callgrind doesn't save the full stack trace so what you
see is a statistical breakdown for callees. It doesn't necessarily mean
that a call path displayed actually exists deeper than its first level.
But the numbers add-up so this is
Hello list!
you may have thought I'd disappeared but here I am, after weeks of working
on a small project of mine. What started as a very small hack for
visualising callgrind's profiles is now an -experimental still- website, a
GCC version of mozilla's "arewefastyet.com". For now you can see i
Monday 22nd of August, 2011: pencils down.
Today my GSOC adventure comes to an end. For whoever doesn't know, this
summer I've been trying to make GCC faster. A task that proved much harder
than I initially thought.
My proposal was about doing many small improvements in various parts of
the
Hi Pierre,
regarding your IRC problems, try a web-based client, for example
http://chat.mibbit.com
Dimitris
r GCC for the first
time. Here goes mine:
I am Dimitrios Apostolou (jimis on IRC) and I live in Heraklion-Crete,
Greece. My project concerns making GCC leaner and faster.
Reading GCC codebase has been a hard exercise for me. In fact it's the
only project I know of that becomes more and more
Hi Jakub,
On Tue, 14 Jun 2011, Jakub Jelinek wrote:
You'd use it as:
void
puthexl (unsigned long value, FILE *f)
{
char buf[2 + CHAR_BIT * sizeof (value) / 4];
if (value == 0)
putc ('0', f);
else
{
char *p = buf + sizeof (buf);
do
*--p = "0123456789abcdef"[value % 16];
Hi Jakub,
On Tue, 14 Jun 2011, Jakub Jelinek wrote:
On Tue, Jun 14, 2011 at 03:13:00PM +0300, Dimitrios Apostolou wrote:
parsing overhead and the hex conversion (implemented suboptimally in
Can you back that up? glibc conversion to hex representation is fairly
heavily optimized, see
Hello list,
I've been working on my project full time since last week, and on a
part-time basis before then. Hopefully I'll be posting updates/patches
more often now that my exams are over. For anyone that wants to talk to
me, I'm jimis on the IRC.
I've looked a little into hash tables, symt
On Fri, 29 Apr 2011, Laurynas Biveinis wrote:
Thanks Diego, please send me the form. I'll sign it as soon as my
contributions require it.
Don't wait; sign it right away - it might take a while to process it.
Hey all, I should have told you, I sent the email so I'm now waiting for
the papers
On Fri, 29 Apr 2011, Diego Novillo wrote:
The very first one is a copyright assignment. Have you started that
process? If not, I will send you the form.
Thanks Diego, please send me the form. I'll sign it as soon as my
contributions require it.
Dimitris
Thank you all for your ideas, they are much appreciated. I will certainly
investigate into the areas you mentioned, so do keep the feedback coming.
I will certainly comment on them, once I have a better understanding. And
I'd like to get in sync with existing work, so that duplicate effort is
a
Hello list,
I am Dimitris (IRC nick: jimis), and this summer I will be working on
optimising GCC, under the umbrella of Google Summer of Code. My proposal
involves profiling and benchmarking in order to detect hotspots in both
CPU and memory usage, and improving or rewriting the respective par
24 matches
Mail list logo
