________________________________________
From: Picorel Javier
Sent: 07 August 2012 17:34
To: Binh Q. Pham
Subject: RE: Internal compiler errors: Segmentation fault

Hi Binh,

Yes we did. Actually, we were able to boot machines running Solaris 10, 
OpenSolaris and Solaris 11 Express.

Regards,
Javier
________________________________________
From: Binh Q. Pham [[email protected]]
Sent: 03 August 2012 21:46
To: Picorel Javier
Cc: [email protected]
Subject: Re: Internal compiler errors: Segmentation fault

Hi Javier,
I see. The biggest problem at our side is that we have spent time trying
to boot a new x86 OS on simics with no luck. Just want to ask: Did you
install a new Solaris OS on simics 3.0?

Thanks,
Binh
On 08/03/2012 08:44 AM, Picorel Javier wrote:
> Hi Binh,
>
> All our booted machines are Sparc. The OS we use is Solaris 10 u9. Therefore, 
> I cannot help you with the x86 Simics problem although there is an official 
> Windriver forum where you can ask for help. Regarding your installation 
> problems, I successfully installed llvm-2.9 in these environments:
>
> 2.6.35-28-generic (Ubuntu)
> gcc 4.4.5
> GNU ld (GNU Binutils for Ubuntu) 2.20.51-system.20100908
> GNU assembler version 2.20.51 (x86_64-linux-gnu) using BFD version (GNU 
> Binutils for Ubuntu) 2.20.51-system.20100908
>
> 2.6.32-131.2.1.el6.x86_64 (Scientific Linux)
> gcc 4.1.2&  gcc 4.6.1
> GNU ld version 2.20.51.0.2-5.11.el6 20091009
> GNU assembler version 2.20.51.0.2 (x86_64-redhat-linux) using BFD version 
> version 2.20.51.0.2-5.11.el6 20091009
>
> My advice is to install llvm on real hardware and then copy the files to a 
> Simics machine. Note that the booted and real machine should have the same OS 
> installed.
>
> Regards,
> Javier
> ________________________________________
> From: Binh Q. Pham [[email protected]]
> Sent: 03 August 2012 00:41
> To: Picorel Javier
> Cc: [email protected]
> Subject: Re: Internal compiler errors: Segmentation fault
>
> Hi Javier,
> I have been trying to follow your instructions, but I have encountered
> some problems:
> 1. I remember I have tried to install a new OS on simics, but the
> installation always crashed. This happened for ubuntu, fedora, and
> gentoo on Simics 3.0. Are you using the same Simics version as mine?
> Also, what OS are you using?
> 2. Because of 1, I decided to install gcc 4.6.1 on the old OS, and I got
> the following error:
> relocation R_X86_64_PC32 against 'simple_object_set_big_16' can not be
> used when making a shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Bad value
> collect2: ld returned 1 exit status
>
> Did the gcc that you are using come with the OS you have on simics? Or
> did you install it from source?
>
> Thank you,
> Binh
> On 07/24/2012 09:01 AM, Picorel Javier wrote:
>> Dear Binh,
>>
>> You need to use a new version of OS as well as install a new version of gcc 
>> (we use 4.6.1).
>>
>> In order to import a workload to Simics, you can follow this procedure:
>> a) On a real machine, install the OS of your interest
>> b) Install the workload on the same machine
>> c) Boot a Simics machine using the same OS that you used on the real machine
>> d) Copy all the workload files (e.g., libraries, workload binaries, etc) to 
>> the Simics machine
>> e) Run and tune the workload inside the Simics machine
>>
>> Regards,
>>
>> Javier
>> ________________________________________
>> From: Binh Q. Pham [[email protected]]
>> Sent: 18 July 2012 18:54
>> To: [email protected]
>> Subject: Internal compiler errors: Segmentation fault
>>
>> Hi everyone,
>> I am trying to set up Cloudsuite on a x86-64 simulated machine running
>> on Simics. The first benchmark I am working on is Software Testing.
>> While building the LLVM, I got a weird error saying that:
>>
>> APInt.cpp: 1960: internal compiler error: Segmentation fault
>>
>> The compiler version is: gcc 4.1.0
>> Operating system version: Fedora Core 5, kernel 2.6.15, x86_64. (This is
>> very old, but this is inside the OS image provided by Simics).
>>
>> Could anyone suggest me what I should do in this case?
>>
>> Thank you very much,
>> Binh

Reply via email to