binaries become larger on 5.1A than on 4.0F
Next message: Florent Boucher: "System crash: invalid memory read access from kernel"
Date: Wed, 26 Nov 2003 14:38:28 +0100
To: tru64-unix-managers@ornl.gov
Hello,
After upgrading our system from 4.0F (PK7) to 5.1A (PK3), we found out
that the C++ binaries of our major application were getting 10 to 35%
larger.
The hardware and source code are identical, we have only changed the OS
and therefore the C++ compiler.
Is there a known explanation for this?
Thanks,
--
Nicolas
Next message: Florent Boucher: "System crash: invalid memory read access from kernel"
Relevant Pages
- SUMMARY: binaries become larger on 5.1A than on 4.0F
... > The hardware and source code are identical, we have only changed the OS ... > Is there a known explanation for this? ... I have asked the question because of a performance problem using these ...
(Tru64-UNIX-Managers) - Re: [Full-Disclosure] THCIISSLame exploit
... The whole idea was binaries vs source code. ... problem with people releasing exploits. ... Yes, but you are able to compile the exploit code yourself, are you not? ...
(Full-Disclosure) - [Full-Disclosure] viruses being sent to list
... First Amendment defines free speech. ... Therefore binaries do not belong to full disclosure. ... Source code postings are exempt from litigation because of the ... 3., Filters only deal with binaries, not source code. ...
(Full-Disclosure) - Re: GPL V3 and Linux - Dead Copyright Holders
... > The point is not only getting access to the source code, ... The hardware may only run signed kernels. ...
(Linux-Kernel) - RE: Possible gpl problem?
... distribution at all can acquire the source code. ... discriminate on the basis of who is trying to enforce the agreement. ... If I say "any third party may hire my services for $200/hr", ... the binaries knows how to obtain the source code. ...
(Linux-Kernel) |
|
