[Openmp-dev] App build error seen with 9.0.1-rc3

[Itaru Kitayama via Openmp-dev]

LIBOMPTARGET_DEBUG=1 gives too much information for some user, so I’d
prefer that part printed out even under the case set to 0.
Otherwise, user cant tell if his app is failing or not.

On Tue, Jan 7, 2020 at 5:58 Rokos, Georgios <georgios.rokos at intel.com>
wrote:

> With LIBOMPTARGET_DEBUG=1 we get the verbose output. In this particular
> case libomptarget says it cannot load the offload entries table for the
> given image, so offload fails. What more is there to print out?
>
>
>
> George
>
>
>
> *From:* Alexey Bataev <a.bataev at hotmail.com>
> *Sent:* Sunday, 5 January, 2020 00:08
> *To:* Alexey Bataev <a.bataev at hotmail.com>; Itaru Kitayama <
> itaru.kitayama at gmail.com>; Rokos, Georgios <georgios.rokos at intel.com>
> *Cc:* openmp-dev <openmp-dev at lists.llvm.org>
> *Subject:* Re: [Openmp-dev] App build error seen with 9.0.1-rc3
>
>
>
> I mean, can we improve it somehow?
>
> Best regards,
>
> Alexey Bataev
>
>
>
> 4 янв. 2020 г., в 17:07, Alexey Bataev <a.bataev at hotmail.com> написал(а):
>
>  Georgios, thoughts?
>
> Best regards,
>
> Alexey Bataev
>
>
>
> 4 янв. 2020 г., в 17:01, Itaru Kitayama <itaru.kitayama at gmail.com>
> написал(а):
>
> 
>
> Alexey,
>
>
>
> When libomptarget fails to initialize the run time environment, shouldn't
> it call out
>
> more descriptive messages than:
>
>
>
> Libomptarget fatal error 1: failure of target construct while offloading
> is mandatory
>
>
>
> ? As this is apparently not due to a developer introduced a bug in his
> application.
>
>
>
>
>
> On Wed, Dec 25, 2019 at 12:38 PM Itaru Kitayama <itaru.kitayama at gmail.com>
> wrote:
>
> Alexey,
>
>
>
> Current trunk just builds my app fine, but upon execution, it fails:
>
>
>
> Libomptarget --> Checking whether device 0 is ready.
> Libomptarget --> Is the device 0 (local ID 0) initialized? 0
> Target CUDA RTL --> Init requires flags to 1
> Target CUDA RTL --> Getting device 0
> Target CUDA RTL --> Max CUDA blocks per grid 2147483647 exceeds the hard
> team limit 65536, capping at the hard limit
> Target CUDA RTL --> Using 1024 CUDA threads per block
> Target CUDA RTL --> Max number of CUDA blocks 65536, threads 1024 & warp
> size 32
> Target CUDA RTL --> Default number of teams set according to library's
> default 128
> Target CUDA RTL --> Default number of threads set according to library's
> default 128
> Libomptarget --> Device 0 is ready to use.
> Target CUDA RTL --> Load data from image 0x0000000010023c70
> Target CUDA RTL --> CUDA module successfully loaded!
> Target CUDA RTL --> Sending global device environment data 4 bytes
> Libomptarget --> Unable to generate entries table for device id 0.
> Libomptarget --> Failed to init globals on device 0
> Libomptarget --> Failed to get device 0 ready
> Libomptarget fatal error 1: failure of target construct while offloading
> is mandatory
>
>
>
> On Wed, Dec 25, 2019 at 11:54 AM Itaru Kitayama <itaru.kitayama at gmail.com>
> wrote:
>
> I'd like to avoid the current trunk to build my app for two reasons: a) it
> takes too much time 40 mins to finish and b) kernel is
>
> not set up properly on the device. So I'd like to obtain a sane working
> stable release like 9.0.0 or 9.0.1-rc3.
>
>
>
> On Wed, Dec 25, 2019 at 11:51 AM Alexey Bataev <a.bataev at hotmail.com>
> wrote:
>
> Can you try to build using trunk?
>
> Best regards,
> Alexey Bataev
>
> > 24 дек. 2019 г., в 21:18, Itaru Kitayama via Openmp-dev <
> openmp-dev at lists.llvm.org> написал(а):
> >
> > 
> > `.text.startup' referenced in section `.init_array.0' of
> /tmp/event_delivery_manager-6b2617.o: defined in discarded section
> `.text.startup[_ZN4nest18DataSecondaryEventIdNS_16GapJunctionEventEE18supported_syn_ids_E]'
> of /tmp/event_delivery_manager-6b2617.o
> > clang-9: error: linker command failed with exit code 1 (use -v to see
> invocation)
> >
> > Can this be a bug in Clang 9? I am trying to build my app to print out
> debugging information from the libomptarget.
> > _______________________________________________
> > Openmp-dev mailing list
> > Openmp-dev at lists.llvm.org
> > https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
>
> _______________________________________________
> Openmp-dev mailing list
> Openmp-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/openmp-dev/attachments/20200107/ffbd92cc/attachment.html>