search for: ftrapping

...t;target-cpu"="x86-64" "target-features"="+cx8,+fxsr,+mmx,+sse,+sse2,+x87" "unsafe-fp-math"="false" "use-soft-float"="false" } --------------------- and the setting "no-trapping-math"="false" should mean -ftrapping-math but it does not and it also contradict with documentation. I think clang should emit this "no-trapping-math"="true" by default if it goes with this assumption https://llvm.org/docs/LangRef.html#floatenv ? what is default behavior of clang -fno-trapping-math or -ftrapping-...

R Help List: Just curious if anyone has successfully built R on a SPARC platform running Sun Solaris 10 using the latest Sun Studio 12 set of compilers. If so, I would be interested in the compile flags that you used. I have tried several different builds of version 2.5.1, 2.6.0, and 2.6.1 using various different compile flags and I am able to compile and check, but for whatever reason, the

...6-64" "target-features"="+cx8,+fxsr,+mmx,+sse,+sse2,+x87" >> "unsafe-fp-math"="false" "use-soft-float"="false" } >> --------------------- >> and the setting "no-trapping-math"="false" should mean -ftrapping-math >> but it does not and it also contradict with documentation. >> >> I think clang should emit this "no-trapping-math"="true" by default if it >> goes with this assumption https://llvm.org/docs/LangRef.html#floatenv ? >> what is default behavio...

Full_Name: Jim Brown Version: 2.6.0 / 2.6.1 OS: Solaris 10 (SPARC) Submission from: (NULL) (35.8.15.102) I have been able to successfully compile version 2.5.1 using the Sun Studio 12 compilers on Sun Solaris 10 (SPARC). All tests using "make check" pass with a status of OK. However, the following section of "reg-tests-1.R" fails when I attempt to test after a build of

About ftrapping-math: I think we should eliminate ftrapping-math, a boolean option, because it overlaps with ffp-exception-behavior, a 3 valued option. Or we can keep it in the clang driver for compatibility, but it should be rewritten by clang driver into ffp-exception-behavior=ignore and ffp-exception-behavior=...

> I think your best bet for controlling code bloat is to compile with > -fsanitize=undefined -fsanitize-trap=undefined. Also you may not need all of UBSan's checks at the same time -- so pick and choose among its checks using the finer-grained flags. If you're really stuck against a hard limit on code size, try applying UBSan to a subset of files in your project at a time. John

An embedded and charset-unspecified text was scrubbed... Name: config.txt Url: https://stat.ethz.ch/pipermail/r-help/attachments/20070501/bdf55878/attachment.txt

...fp-model=[strict|except] is being developed in the D53157 patch, and there is current llvm support for the fast settings by using the fast math flags llvm::FastMathFlags. Note: the clang-cl wrapper to support Microsoft options has simplified support for these options by mapping /fp-model=except to ftrapping-math, fp-mdel=fast to ffast-math, fp-model=precise and fp-model=strict to fno-fast-math (see clang/Driver/CLCompatOptions.td). According to the online options documentation, you can combine except[-] with [precise|strict|fast], but combining both fast and except is not a valid setting (the Driver...

...is is something we should consider adding. > the granularity of these knobs is also interesting (expression, code block, function or translation unit), iso c pragmas work on code block level. I'd have to defer to someone more familiar with the front end to say how that is handled. > -ftrapping-math vs -ffp-exception-behaviour=maytrap is unclear. The "maytrap" setting is supposed to prevent the optimizer from introducing spurious exceptions (e.g. speculative execution) while still allowing it to optimize away potential exceptions (e.g. dce operations whose results are never use...

...t. This takes into account both the semantics of the #pragma as defined by the standard, and the implementation-defined default rules that apply to code outside of any #pragma. GCC currently has the following two related command-line options: -frounding-math: Do not assume default rounding mode -ftrapping-math: Assume FP operations may trap clang accepts but (basically) ignores those options. As a first step, it might make sense to have the FENV_ACCESS default behavior triggered by these options, even while the front end does not yet support the actual #pragma. The front end then needs to transmi...

Hi all, I'm trying to put together a set of rules for how the various floating point semantic modes should be handled in clang. A lot of this information will be relevant to other front ends, but the details are necessarily bound to a front end implementation so I'm framing the discussion here in terms of clang. Other front ends can choose to follow clang or not. The existence of this set

Just a "heads up". I tried to search mailinglist archives and wiki, but found no similar configurations. Dovecot is unbuildable with the following configuration: SunOS mail 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Fire-V210 cc: Forte Developer 7 C 5.4 2002/03/09 config.log output from ./configure is at: http://iso.ego.fi/misc/dovecot_1.0-test50.log I guess I'll have to bend

...both the semantics of the #pragma as defined by the standard, > and the implementation-defined default rules that apply to code > outside of any #pragma. GCC currently has the following two > related command-line options: > > -frounding-math: Do not assume default rounding mode > -ftrapping-math: Assume FP operations may trap > > clang accepts but (basically) ignores those options. As a first > step, it might make sense to have the FENV_ACCESS default > behavior triggered by these options, even while the front end > does not yet support the actual #pragma. > > The...

...f the #pragma as defined by the standard, > and the implementation-defined default rules that apply to code > outside of any #pragma. GCC currently has the following two > related command-line options: > > -frounding-math: Do not assume default rounding mode > -ftrapping-math: Assume FP operations may trap > > clang accepts but (basically) ignores those options. As a first > step, it might make sense to have the FENV_ACCESS default > behavior triggered by these options, even while the front end > does not yet support the actual #pragm...

Hello, I''m having problems compiling Ruby 1.8.5 on a 64-bit Intel machine running Solaris 10 U3. I''m using Sun Studio 12 for building an optimized package for our company. We''re not interested in coolstack (from Sun used with GCC). Any help below would be appreciated: root@host # uname -an SunOS host 5.10 Generic_125101-08 i86pc i386 i86pc Solaris root@host # isainfo

...e #pragma as defined by the standard, >> and the implementation-defined default rules that apply to code >> outside of any #pragma. GCC currently has the following two >> related command-line options: >> >> -frounding-math: Do not assume default rounding mode >> -ftrapping-math: Assume FP operations may trap >> >> clang accepts but (basically) ignores those options. As a first >> step, it might make sense to have the FENV_ACCESS default >> behavior triggered by these options, even while the front end >> does not yet support the actual #p...

> On Jul 21, 2017, at 6:04 AM, Shi, Steven via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >>> I think your best bet for controlling code bloat is to compile with >>> -fsanitize=undefined -fsanitize-trap=undefined. >> >> Also you may not need all of UBSan's checks at the same time -- so pick >> and choose among its checks using the