X-Git-Url: https://git.llucax.com/personal/website.git/blobdiff_plain/82c67a166ee0d3d8893c3ae1e84f91f067045fd0..3ee8da73d904a64ada1719945e7b8467e6c0c60a:/source/blog/posts/2010/07/13-performance-wtf.rst

diff --git a/source/blog/posts/2010/07/13-performance-wtf.rst b/source/blog/posts/2010/07/13-performance-wtf.rst
index b93de2e..c8c8577 100644
--- a/source/blog/posts/2010/07/13-performance-wtf.rst
+++ b/source/blog/posts/2010/07/13-performance-wtf.rst
@@ -17,7 +17,7 @@ a Makefile__ to compile the programs, run the tests and generate some graphs
 with the timings to compare the performance against the current D__ GC__
 (Tango__ really).
 
-__ http://www.llucax.com.ar/proj/dgc/index.html
+__ /proj/dgc/index.html
 __ http://en.wikipedia.org/wiki/Garbage_collection_%28computer_science%29
 __ http://en.wikipedia.org/wiki/Makefile
 __ http://digitalmars.com/d/index.html
@@ -103,7 +103,7 @@ box, and the box at work are both 64 bits, I suspected from that too, but the
 old AMD is 32 bits and I see the problem there too.
 
 __ http://www.dsource.org/projects/dmd
-__ http://www.llucax.com.ar/blog/blog/post/-41d8f86f
+__ /blog/blog/post/-41d8f86f
 
 I've tried valgrind__ + callgrind__ + kcachegrind__ but it seems like valgrind
 emulation is not affected by whatever difference is when the program is ran
@@ -144,7 +144,7 @@ I'll revert it if it does, no matter what happen with this issue.
 If you have any ideas on what could be going on, **anything**, please let me
 know (in a comment of via e-mail__). Thanks :)
 
-__ mailto: luca@llucax.com.ar
+__ mailto: luca@llucax.com
 
 
 .. admonition:: Update