<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class="">NVPTX does not expose a float128 type; nor do we have any negative tests for it. Any such change to float128 support should not be enabled for the NVPTX target.</div>
<br class="">
<div>
<blockquote type="cite" class="">
<div class="">On Mar 29, 2016, at 6:06 AM, Nemanja Ivanovic <<a href="mailto:nemanja.i.ibm@gmail.com" class="">nemanja.i.ibm@gmail.com</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div class="">
<div class="">
<div class="">To date, I have not received any responses on this. I'm forwarding this message again to see if I can get some responses regarding this __float128 patch. I don't want to break anyone with this commit so I hope to discuss this with target maintainers
before I commit.<br class="">
</div>
I am sending the message to the target maintainers listed in CODE_OWNERS.TXT, so if I've sent it to you erroneously, I apologize.<br class="">
<br class="">
</div>
Sincerely,<br class="">
</div>
Nemanja Ivanovic<br class="">
<div class="">
<div class="">
<div class=""><br class="">
<div class="">
<div class="gmail_quote">---------- Forwarded message ----------<br class="">
From: <b class="gmail_sendername">Nemanja Ivanovic</b> <span dir="ltr" class=""><<a href="mailto:nemanja.i.ibm@gmail.com" class="">nemanja.i.ibm@gmail.com</a>></span><br class="">
Date: Fri, Mar 25, 2016 at 5:09 PM<br class="">
Subject: Target support for __float128 in the front end<br class="">
To: <a href="mailto:cfe-dev@lists.llvm.org" class="">cfe-dev@lists.llvm.org</a><br class="">
<br class="">
<br class="">
<div dir="ltr" class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="">Hi everyone,<br class="">
<br class="">
</div>
I plan to commit the changeset listed in the Phabricator review 15120 (<a href="http://reviews.llvm.org/D15120" target="_blank" class="">http://reviews.llvm.org/D15120</a>) which will impact the way Clang treats the
<span style="font-family:monospace,monospace" class="">__float128</span> type, keyword, etc.<br class="">
<br class="">
</div>
Namely, we currently have a workaround that allows Clang to parse some C++ headers (such as type_traits) since they contain template specializations for
<span style="font-family:monospace,monospace" class="">__float128</span>. However, this patch establishes that type as a builtin type, enables the keyword and allows for literals of the type. Since not all targets have support for what that type is supposed
to represent (i.e. a 128-bit floating point type with IEEE quad-precision semantics), the default behaviour for all targets is to not enable the type.<br class="">
<br class="">
</div>
<div class=""><b class="">The problem:</b><br class="">
</div>
This puts targets on which gcc has <span style="font-family:monospace,monospace" class="">
__float128</span> support in a situation where they may not be able to compile programs that include the aforementioned headers. Namely, if the configuration defines
<span style="font-family:monospace,monospace" class="">_GLIBCXX_USE_FLOAT128</span> and the
<span style="font-family:monospace,monospace" class="">__float128</span> type is not enabled in Clang, anything that includes the header will not compile.<br class="">
<br class="">
</div>
<b class="">The solution:</b><br class="">
</div>
Any target that needs to enable support for this type can do so by overriding <span style="font-family:monospace,monospace" class="">
TargetInfo::hasFloat128Type()</span>. When doing so, there may be a small number of test cases that needs to change if they rely on this support not being enabled.<br class="">
<br class="">
</div>
I would appreciate it if you would let me know if your target needs to have this support enabled and if you would be OK with me committing this patch. As much as I would like to take on as much of this work as possible, please understand that I do not have
access to hardware to allow me to test any impact to your target if I were to make the change myself (of course, I'm referring to things that can't be caught by the Clang test cases).<br class="">
<br class="">
</div>
Thank you,<br class="">
<br class="">
</div>
Nemanja<br class="">
</div>
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
<DIV>
<HR>
</DIV>
<DIV>This email message is for the sole use of the intended recipient(s) and may
contain confidential information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy all copies of the original
message. </DIV>
<DIV>
<HR>
</DIV>
</body>
</html>