There are some there, but they are rather old. The target you should be looking for is: alpha-unknown-linux-gnu. alpha-dec-vms would be for the VMS operating system, not linux.
If you want to compile you're own compiler, http://crosstool-ng.org is probably your best bet. Ali On May 2, 2013, at 7:43 PM, mehmet basaran <[email protected]> wrote: > Hi again, > > After 1 week spent on building a cross compiler for alpha-dec-vms > which turned out unsuccessful, I find out now that there might be > precompiled compilers on > > http://www.m5sim.org/Download > > So I'll confirm after I try them out. > > Thanks > > 2013/5/3 mehmet basaran <[email protected]>: >> Hi Ali, >> >> Thanks for your response. I downloaded the patches and applied it to >> kernel-2.26. But in order to build it I need a cross compiler for >> alpha arch. >> >> So I have been trying to build one. Which version of gcc would you >> suggest using? And I couldn't figure out what my target platform would >> be. I tried to compile for alpha-dec-vms using gcc-4.8.0 and >> bin-utils-2.23 but could find the required resources. >> >> Do you have any suggestions on this matter as well? >> >> Thanks a lot >> Regards >> >> Mehmet >> >> 2013/4/24 Ali Saidi <[email protected]>: >>> Hi Mehmet, >>> >>> You have to have a kernel that has some symbols (like thread_info_size, >>> thread_info_task, …) in it so gem5 can find these values. >>> You probably need to add these to your kernel: >>> http://repo.gem5.org/linux-patches/file/0ab58d9bd9a5/m5/m5struct.diff >>> >>> Ali >>> >>> >>> >>> >>> On Apr 22, 2013, at 8:11 AM, mehmet basaran <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> I am trying to get the software thread-ids per memory access in an >>>> application. After some research I found out that this might be >>>> implemented in ALPHA system. SO I modified the code a little bit to get >>>> the memory trace per thread. >>>> >>>> in src/mem/request.hh >>>> I included additional variables to hold thread related info. >>>> >>>> in src/cpu/simple/atomic.cc >>>> in AtomicSimpleCPU::init() I tried to get thread_info and put it in request >>>> >>>> Linux::ThreadInfo threadInfo(tc); >>>> ifetch_req.setThreadInfo(threadInfo.curTaskName(), >>>> threadInfo.curTaskPID(), threadInfo.curTaskStart(), >>>> threadInfo.curThreadInfo()); >>>> ... >>>> >>>> After that I print those info in corresponding trace flags. These values >>>> are; >>>> curTaskName() = "" >>>> curTaskPID() = 0 >>>> curTaskStart() = 0 >>>> curThreadInfo() = 0 >>>> >>>> I think they do not provide any real info considering my application has >>>> omp 4 threads. >>>> >>>> My questions are; >>>> >>>> 1. Where is this functionality is implemented in ALPHA mode? >>>> 2. Any pointers on how I can get these values from kernel? >>>> >>>> Any help on the matter is greatly appreciated. >>>> Regards. >>>> >>>> Mehmet >>>> _______________________________________________ >>>> gem5-users mailing list >>>> [email protected] >>>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >>> >>> _______________________________________________ >>> gem5-users mailing list >>> [email protected] >>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
