أمثلة عملية من IQ Option و Pocket Option

From binaryoption
Revision as of 08:54, 7 March 2025 by Admin (talk | contribs) (@pipegas from Special:WantedPages)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Баннер1

مقدمة

تعد منصات التداول مثل IQ Option وPocket Option من أفضل المنصات المتاحة للمتداولين العرب الذين يرغبون في دخول عالم تداول الخيارات الثنائية. هذه المنصات توفر أدوات متقدمة وواجهات سهلة الاستخدام، مما يجعلها مثالية للمبتدئين والمحترفين على حد سواء. في هذا المقال، سنقدم أمثلة عملية وإرشادات خطوة بخطوة لمساعدة المبتدئ# [PATCH] D117926: [OpenMP][FIX] Ensure device IDs are properly passed to the runtime Johannes Doerfert via Phabricator via llvm-commits llvm-commits at lists.llvm.org Fri Jan 21 16:38:56 PST 2022 jdoerfert added a comment.

In D117926#3277890 <https://reviews.llvm.org/D117926#3277890>, @tianshilei1992 wrote:

> In D117926#3277546 <https://reviews.llvm.org/D117926#3277546>, @jdoerfert wrote: > >> In D117926#3277166 <https://reviews.llvm.org/D117926#3277166>, @tianshilei1992 wrote: >> >>> I think the problem is it's a bit unclear what the runtime wants for the device ID. Because in OpenMP, the device ID is determined by the runtime, and it's possible the user-provided device ID is not the one the runtime uses, which is the case in libomptarget. So it should be fine to pass the user's device ID here since we are not using it in the runtime anyway (the runtime is going to use its own device ID anyway). But if someone in the future wants to use this value, it should be the one that the runtime uses, not the user uses. >> >> That's a good point. We should probably set the device ID in the runtime and then pass it back. Or we need to make sure it is well defined what we expect here. >> >> @Meinersbur, what do you think? > > Yes, that's why in `omp_target_alloc`, we need to use the device ID returned by `__tgt_target` rather than the one passed by the user, because it's the one used by the runtime. But I think it's up to the runtime to decide what to do with the user-provided device ID. I'm not sure if this is the same for other runtimes, but for libomptarget, as long as it's not used, it should be fine to pass the user's device ID. But the API should be clear about this.

I agree we should probably not set it in the runtime but instead pass the user provided one and let the runtime decide what to do with it. So I think this change is fine.

====

Comment at: llvm/lib/Frontend/OpenMP/OMPIRBuilder.cpp:2856 + // If we are in target region, we use the device ID from the offloading entry + if (IsTargetDevice) + DeviceID = Builder.getInt32(OMPBuilder.getDeviceID());

What is this now doing? It looks like this is only relevant for the device compilation as you mentioned. Is this the device ID of the host as it exists in the device code? Should we just remove this and use the one passed in always?

====

Comment at: llvm/lib/Frontend/OpenMP/OMPIRBuilder.cpp:2862 + // If we are in target region, we use the device ID from the offloading entry + if (IsTargetDevice) + DeviceID = Builder.getInt32(OMPBuilder.getDeviceID());

Same here ^

Repository:

 rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION

 https://reviews.llvm.org/D117926/new/

https://reviews.llvm.org/D117926

More information about the llvm-commits mailing list

ابدأ التداول الآن

سجل في IQ Option (الحد الأدنى للإيداع $10)

افتح حساباً في Pocket Option (الحد الأدنى للإيداع $5)

انضم إلى مجتمعنا

اشترك في قناة Telegram الخاصة بنا @strategybin للحصول على: ✓ إشارات تداول يومية ✓ تحليلات استراتيجية حصرية ✓ تنبيهات باتجاهات السوق ✓ مواد تعليمية للمبتدئين

Баннер