Titen Lev Distro - Anybody installed it?

Titen Lev http://www.affordy.com/ Has anyone installed the Distro? I saw the link in l ___ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il

Re: toolchain's output depends on toolchain used to build the compiler?

Yedidyah Bar-David wrote: (with your client's permission, if applicable). I know that gcc can optimize on a larger scope than a function, but this might work. There's the rub. These are on a classified network that requires the MoD to sign off on such a thing. Not likely. Shachar -- Shach

Re: toolchain's output depends on toolchain used to build the compiler?

I'd like to second Yedidyah's suggestion and re-express it as an application of the "Lion in the desert" methodology. The "desert division into halves by fences" can proceed along at least two dimensions: 1. Reduction of the size of a module which compiles differently in the two platforms (Yedidy

Re: toolchain's output depends on toolchain used to build the compiler?

On Wed, Feb 10, 2010 at 04:06:32AM +0200, Shachar Shemesh wrote: > Again, thank you for trying to help, but lets try to move forward. Well, you obviously expected an answer from someone that either knows gcc well enough to give an answer off the top of their head, or from someone that such a thing

Re: toolchain's output depends on toolchain used to build the compiler?

Omer Zak wrote: I suggested before to check the compiler and linker flags which are actually used. Now I decided to check how to actually make the checks. According to man gcc: -v (verbose mode) reports the final form of the include path. --help -v reports extra information which can be helpful

Re: toolchain's output depends on toolchain used to build the compiler?

I suggested before to check the compiler and linker flags which are actually used. Now I decided to check how to actually make the checks. According to man gcc: -v (verbose mode) reports the final form of the include path. --help -v reports extra information which can be helpful. I found that fo

Re: toolchain's output depends on toolchain used to build the compiler?

Oleg Goldshmidt wrote: 2010/2/9 Shachar Shemesh > The newlib libraries built are compared, and are identical down to the last assembly instruction. The client libraries are compared. Some are identical, some are not. Just to dot all the i's and cross

[TelFOSS] Next Meeting: "vtiger CRM" on 14-Feb-2010

(הגרסה בעברית תבוא בהמשך ההודעה.) Hi all! The Tel Aviv Open Source Club will host a talk by Rami Addady about "vtiger CRM, the open-source Customer Relations Management Program"- on Sunday 14- February-2010. The meeting will take place at Tel Aviv University, at Holcblat Hall (No. 007) on the

RE: toolchain's output depends on toolchain used to buildthe compiler?

So the next step would be to compile a test program ("Hello, World!" or the moral equivalent) on both platforms, send outputs of 'gcc -v' (or 'gcc -###'), -E and -S as well as the objdumps to the list (or a link to where interested parties can download these). Rony ___

Re: toolchain's output depends on toolchain used to build the compiler?

2010/2/9 Shachar Shemesh > > The newlib libraries built are compared, and are identical down to the last > assembly instruction. The client libraries are compared. Some are identical, > some are not. > Just to dot all the i's and cross all the t's: are the cross-binutils identical? -- Oleg Gol

Re: toolchain's output depends on toolchain used to build the compiler?

On Tue, 2010-02-09 at 12:23 +0200, Shachar Shemesh wrote: > Omer Zak wrote: > > This could catch blocks created from uninitialized (or > > differently-initialized) memory areas. > > > In my software or in the compiler's? In the compiler's or the linker's. Another idea: Are you absolutely sur

Re: toolchain's output depends on toolchain used to build the compiler?

Omer Zak wrote: On Tue, 2010-02-09 at 11:26 +0200, Shachar Shemesh wrote: Orna Agmon Ben-Yehuda wrote: If the absolute path is included (I think -g does that). The mount point in the two environments may be called differently. That's why I'm using objdump -d, which does no

Re: toolchain's output depends on toolchain used to build the compiler?

On Tue, 2010-02-09 at 11:26 +0200, Shachar Shemesh wrote: > Orna Agmon Ben-Yehuda wrote: > > > > If the absolute path is included (I think -g does that). The mount > > point in the two environments may be called differently. > > > That's why I'm using objdump -d, which does not print the source

Re: toolchain's output depends on toolchain used to build the compiler?

Omer Zak wrote: Further questions and things to eliminate: 1. Are there timestamps in the machine code files (presumably embedded by the linker, because the compile-time ones don't exist, by checking for identical post-preprocessor files)? None that get printed by "objdump -d". That's just th

Re: toolchain's output depends on toolchain used to build the compiler?

Orna Agmon Ben-Yehuda wrote: 2010/2/9 Shachar Shemesh > ronys wrote: Hi Shachar, Interesting problem. Here are some thoughts: Can you control the level of optimization used by the customer? Does -O0 create identical object code?

Re: toolchain's output depends on toolchain used to build the compiler?

On Tue, 2010-02-09 at 10:52 +0200, Shachar Shemesh wrote: > ronys wrote: > > What are the differences in code? Perhaps they're related to the > > different paths? (If the lengths of the paths are different, and > > they're stored somewhere in the object code, that'll change the > > results) > Th

Re: toolchain's output depends on toolchain used to build the compiler?

2010/2/9 Shachar Shemesh > ronys wrote: > > Hi Shachar, > > Interesting problem. Here are some thoughts: > > Can you control the level of optimization used by the customer? Does -O0 > create identical object code? > > Havn't tested yet, but my gut feeling is "yes". > > What are the differences

RE: toolchain's output depends on toolchain used to build the compiler?

Further questions and things to eliminate: 1. Are there timestamps in the machine code files (presumably embedded by the linker, because the compile-time ones don't exist, by checking for identical post-preprocessor files)? 2. The difference in paths suggested by Rony could also be due to different

Re: toolchain's output depends on toolchain used to build the compiler?

ronys wrote: Hi Shachar, Interesting problem. Here are some thoughts: Can you control the level of optimization used by the customer? Does -O0 create identical object code? Havn't tested yet, but my gut feeling is "yes". What are the differences in code? Perhaps they're related to the di

RE: toolchain's output depends on toolchain used to build the compiler?

Hi Shachar, Interesting problem. Here are some thoughts: Can you control the level of optimization used by the customer? Does -O0 create identical object code? What are the differences in code? Perhaps they're related to the different paths? (If the lengths of the paths are different, and the