www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/1996/06/22/12:51:59

From: k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at (Oberhumer Markus)
Message-Id: <199606221644.SAA01348@c210.edvz.uni-linz.ac.at>
Subject: linking speedup ?
To: djgpp-workers AT delorie DOT com
Date: Sat, 22 Jun 1996 18:44:40 -0200 (MET DST)
Return-Read-To: markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at

===============================================================================
Markus F.X.J. Oberhumer <markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at>

Subject: linking speedup ?
To: djgpp-workers AT delorie DOT com
===============================================================================

I have noticed that the linking process of bigger programs (e.g. a C++
program with debug info) is very slow when delayed-write disk cache is
disabled (as I do because of safety reasons).

After a look at the specs I suspect this is because gcc calls stubify
after ld created the COFF image. Is this true ?

If yes, would it be much work to add the functionality
of stubify to ld if the output file ends in '.exe',
thereby saving a write and read of the image ?

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019