Hi kalle,
Thanks for quick response.
> 1. The build rules for the required files are listed in
lib/CL/Makefile.am.
Does this Makefile.am include the files required for driver? Let's says for
example, i 'pthread' driver, how does this Makefile.am use the required
files for 'pthread' driver?
2. sure, the hardware i mean was a co-processor. I would write a driver
similar to 'cellspu'. Can you tell me how to include newly added source
files in lib/CL/Makefile.am, to be reflected in libpocl.so file? Or shall I
need to add these newly added source files in some other makefile?
Regards,
Gopal
On Sun, Dec 8, 2013 at 1:16 AM, <[email protected]>wrote:
> Send pocl-devel mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/pocl-devel
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of pocl-devel digest..."
>
>
> Today's Topics:
>
> 1. Re: LLVM API mode ready for enabling by default (Kalle Raiskila)
> 2. Re: LLVM API mode ready for enabling by default
> (Pekka J??skel?inen)
> 3. Re: LLVM API mode ready for enabling by default
> (Pekka J??skel?inen)
> 4. Re: LLVM API mode ready for enabling by default
> (Pekka J??skel?inen)
> 5. implementation of libpocl.so (Gopal Rastogi)
> 6. Re: implementation of libpocl.so (Kalle Raiskila)
> 7. ASM_DRIVER_WORKAROUND (Erik Schnetter)
> 8. Re: ASM_DRIVER_WORKAROUND (Kalle Raiskila)
> 9. Re: ASM_DRIVER_WORKAROUND (Erik Schnetter)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Nov 2013 18:49:13 +0200
> From: Kalle Raiskila <[email protected]>
> Subject: Re: [pocl-devel] LLVM API mode ready for enabling by default
> To: Portable Computing Language development discussion
> <[email protected]>
> Message-ID: <20131127184913.21deeff8@atom>
> Content-Type: text/plain; charset=US-ASCII
>
> Pekka wrote on 2013-11-27:
>
> >
> > What is the situation now with the --llvm-api on MacOS, PPC, ARM?
> > Is it now OK to turn it on by default?
> >
>
> PPC has one unexpected fail with --llvm-api, that strange 'unresolved
> symbols' when loading the parallel.so. I think this might even be
> unrelated to using the api, and due to some other trouble on this
> platform. Does anyone else have a PPC to test pocl on?
>
> ARM has been more-or-less broken since pocl started to generate
> ARMv7/cortex-a8 binaries, so I cannot say what effect the llvmapi mode
> has. We'll know more once the addressspace issue is solve.
>
>
> kalle
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 27 Nov 2013 19:34:40 +0200
> From: Pekka J??skel?inen <[email protected]>
> Subject: Re: [pocl-devel] LLVM API mode ready for enabling by default
> To: Kalle Raiskila <[email protected]>
> Cc: Portable Computing Language development discussion
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 11/27/2013 06:49 PM, Kalle Raiskila wrote:
> > ARM has been more-or-less broken since pocl started to generate
> > ARMv7/cortex-a8 binaries, so I cannot say what effect the llvmapi mode
> > has. We'll know more once the addressspace issue is solve.
>
> I'll fix that in the TargetAddressSpaces pass where we can scan through
> all pointercasts generated in pocl, those have to be reverted back
> to bitcasts after/during "AS flattening".
>
> Anyways, the addresspace-issue is only happening with LLVM 3.3 and should
> not
> be related to LLVM API mode. So, perhaps I should just switch it on
> by default and get it over with? The scripts mode will be there as
> a fall back in the 0.9 release anyways.
>
> --
> Pekka
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 28 Nov 2013 13:52:54 +0200
> From: Pekka J??skel?inen <[email protected]>
> Subject: Re: [pocl-devel] LLVM API mode ready for enabling by default
> To: Kalle Raiskila <[email protected]>
> Cc: Portable Computing Language development discussion
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> OK,
>
> I pushed a potential fix for ARM LLVM 3.4. Please test as I do not have
> an ARM box.
>
> On 11/27/2013 07:34 PM, Pekka J??skel?inen wrote:
> > I'll fix that in the TargetAddressSpaces pass where we can scan through
> > all pointercasts generated in pocl, those have to be reverted back
> > to bitcasts after/during "AS flattening".
>
>
> --
> Pekka
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 29 Nov 2013 11:13:00 +0200
> From: Pekka J??skel?inen <[email protected]>
> Subject: Re: [pocl-devel] LLVM API mode ready for enabling by default
> To: Portable Computing Language development discussion
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> LLVM API mode is now the default.
> You can use the (now deprecated) shell scripts with
> configure --disable-llvmapi.
>
> Only the llc/clang binaries are now called via system() for generating and
> linking the final kernel binary from the work-group function bitcode, but
> the shell scripts are not used in the process. This can be replaced with
> LLVM JIT API calls later.
>
> On 11/21/2013 10:19 AM, Pekka J??skel?inen wrote:
> > I plan to enable the LLVMAPI mode by default
>
>
> --
> Pekka
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 6 Dec 2013 19:08:47 +0530
> From: Gopal Rastogi <[email protected]>
> Subject: [pocl-devel] implementation of libpocl.so
> To: [email protected]
> Message-ID:
> <CAGXiX+8NRv-9+zCVYXLy-ASz_bk=
> [email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi everyone,
>
> I am a developer and want to modify "libpocl.so" library, to detect a new
> hardware device using existing pocl-0.8 code.
> I have downloaded and successfully installed pocl-0.8 in my system.
> After installing, I copied the path of installed shared library i.e
> "libpocl.so" into /etc/OpenCL/vendors/pocl-tests.icd file. Now when I ran
> the clinfo command, I got Portable Computing Language as OpenCL platform
> and pthread as OpenCL device.
>
> 1. The first thing I want to know the dependency of libpocl.so, i mean
> which file are being used to generate libpocl.so file?
> 2. Secondly, which file shall I need to modify/rewrite in order to detect a
> new hardware?
> 3. Apart from this, what else I need to consider in order to detect a new
> hardware device?
>
> Thanks and Regards,
> Gopal
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 6
> Date: Sat, 7 Dec 2013 14:29:23 +0200
> From: Kalle Raiskila <[email protected]>
> Subject: Re: [pocl-devel] implementation of libpocl.so
> To: [email protected]
> Message-ID: <20131207142923.7725de73@atom>
> Content-Type: text/plain; charset=US-ASCII
>
> Hello Gopal
>
> Gopal wrote on 2013-12-06:
>
> > 1. The first thing I want to know the dependency of libpocl.so, i mean
> > which file are being used to generate libpocl.so file?
>
> The build rules with required files and libraries are listed in
> lib/CL/Makefile.am
> The source files listed there you probably will not need to touch at
> all, though.
>
> > 2. Secondly, which file shall I need to modify/rewrite in order to
> > detect a new hardware?
>
> I assume here the new hardware you speak of is a
> peripheral/co-processor, not just a new host processor type.
>
> You need to write a driver for your hardware. This driver then detects
> and handles any communication with your hardware. Look in
> lib/CL/devices/, there are four drivers there currently. 'Basic' and
> 'pthreads' run on the host CPU, 'tce' and 'cellspu' run on external
> processors. Of these two 'tce' is much more complete than the cellspu.
>
> > 3. Apart from this, what else I need to consider in order to detect a
> > new hardware device?
>
> The macros that need to be modified when adding a new driver was cleaned
> up since 0.8, so I suggest using the latest version of pocl from
> github. Also, pocl 0.9 is just around the corner.
>
> kalle
>
>
>
> ------------------------------
>
> Message: 7
> Date: Sat, 7 Dec 2013 11:18:01 -0500
> From: Erik Schnetter <[email protected]>
> Subject: [pocl-devel] ASM_DRIVER_WORKAROUND
> To: Portable Computing Language development discussion
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> Can we enable ASM_DRIVER_WORKAROUND for all architectures? Did someone try
> this?
>
> It is necessary for armv6 as well, and seems to work fine on x86-64 (OS X).
>
> -erik
>
> --
> Erik Schnetter <[email protected]>
> http://www.perimeterinstitute.ca/personal/eschnetter/
>
> My email is as private as my paper mail. I therefore support encrypting
> and signing email messages. Get my PGP key from http://pgp.mit.edu/.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 203 bytes
> Desc: Message signed with OpenPGP using GPGMail
>
> ------------------------------
>
> Message: 8
> Date: Sat, 7 Dec 2013 19:28:56 +0200
> From: Kalle Raiskila <[email protected]>
> Subject: Re: [pocl-devel] ASM_DRIVER_WORKAROUND
> To: [email protected]
> Message-ID: <20131207192856.17e3e88c@atom>
> Content-Type: text/plain; charset=US-ASCII
>
> Erik wrote on 2013-12-07:
>
> > Can we enable ASM_DRIVER_WORKAROUND for all architectures? Did
> > someone try this?
>
> It was originally on for all, but this broke the PPC32 "cross" build,
> i.e. the assembly files did not encode ppc32, and were assembled
> into ppc64 elf objects.
>
>
> kalle
>
>
>
> ------------------------------
>
> Message: 9
> Date: Sat, 7 Dec 2013 14:46:17 -0500
> From: Erik Schnetter <[email protected]>
> Subject: Re: [pocl-devel] ASM_DRIVER_WORKAROUND
> To: Portable Computing Language development discussion
> <[email protected]>
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> On Dec 7, 2013, at 12:28 , Kalle Raiskila <[email protected]> wrote:
>
> > Erik wrote on 2013-12-07:
> >
> >> Can we enable ASM_DRIVER_WORKAROUND for all architectures? Did
> >> someone try this?
> >
> > It was originally on for all, but this broke the PPC32 "cross" build,
> > i.e. the assembly files did not encode ppc32, and were assembled
> > into ppc64 elf objects.
>
> I will try to introduce HOST_AS_FLAGS that can be set either to
> HOST_CLANG_FLAGS (e.g. for the case above) or to "-float-abi-hard" (for
> ARM). I'm testing this on a branch now.
>
> -erik
>
> --
> Erik Schnetter <[email protected]>
> http://www.perimeterinstitute.ca/personal/eschnetter/
>
> My email is as private as my paper mail. I therefore support encrypting
> and signing email messages. Get my PGP key from http://pgp.mit.edu/.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 203 bytes
> Desc: Message signed with OpenPGP using GPGMail
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
>
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>
> ------------------------------
>
> _______________________________________________
> pocl-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/pocl-devel
>
>
> End of pocl-devel Digest, Vol 27, Issue 1
> *****************************************
>
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel
