Displaying 20 results from an estimated 800 matches similar to: "[Unsafe-fp-math] Merge attribute for inlining"
2018 Dec 04
2
[Unsafe-fp-math] Merge attribute for inlining
Hal,
Thanks for the reply. I am trying to understand the underlying concern. That means the inlining of a callee without unsafe-fp-math attribute set will block the unsafe optimization in its caller, right?
Thanks,
Yan
From: Finkel, Hal J. [mailto:hfinkel at anl.gov]
Sent: Tuesday, December 4, 2018 11:34 AM
To: Yan Luo <yan.luo2 at synopsys.com>; llvm-dev at lists.llvm.org
Subject: Re:
2003 Feb 18
0
syslinux: possibly unsafe permissions for /tmp
Hi all. I keep getting the error in the subject line whenever attempting
to put Syslinux onto the floppy. As a result, it refuses to write
ldlinux.sys. I have tried most if not all the viable combinations, and
Syslinux still complains. Anyone know what permissions Syslinux espect on
/tmp? I have not been able to determine this so far. Thanks!
Yours
Li Haijun
2000 Jan 19
0
safe_strcpy is unsafe
On Thu, Jan 20, 2000 at 08:27:05AM +1100, Michael Stockman wrote:
> safe_strcpy is not very safe. It seems that it writes 1 char longer
> than maxlen, which is bad if the buffer isn't that long. Example of
> bad but common usage:
>
> pstring str;
> safe_strcpy( str, "Hello world", sizeof(str) );
>
> This may cause a SIGSEGV!
Unfortunately safe_strcpy was
2004 Dec 28
1
"No locking available.Running Samba would be unsafe"
Hello again,
I sent in this error a couple weeks ago and one person (eric) kindly
responded
and tried to help, but to no avail. Any one else have any ideas on the
following:
A couple years ago I installed Samba 2.2.0 on our HP9000 running HPUX 10.20.
I am now trying to install it on a customer's HP9000 (also using 10.20) and
executing
the configure command produces the "No locking
2005 Oct 06
0
[Bug 3147] New: message 'copying unsafe symlink' only appears if verbose>=2
https://bugzilla.samba.org/show_bug.cgi?id=3147
Summary: message 'copying unsafe symlink' only appears if
verbose>=2
Product: rsync
Version: 2.6.7
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P3
Component: core
AssignedTo: wayned@samba.org
2011 Feb 01
1
[PATCH] libxl: fix unsafe subtraction in libxl_set_memory_target
The current libxl_set_memory_target function subtracts a negative amount
from an uint32_t variable without checking if the operation wraps
around.
This patch fixes this bug (that I previously believed to be an
hypervisor issue):
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1729
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
diff -r a69965e61ae9
2018 Mar 23
0
Optimization: Replace functions with thread unsafe variants + detection of multithreading
Hello,
My idea is to detect a multithreading and perform some transformations and
get new possibilities for optimizations:
1. Check pthread_create and follow CallInstr (goal: to know that we are in
new thread), identify functions where fork is used and check all other
CallIstr (we are in child) + check Windows variants of fork/ thread create..
2. Check functions if they do not contain any of
2004 Jun 05
2
Register parameters are unsafe with gcc 3.3.2
I have the following toolchain:
$ ld --version
GNU ld version 2.15.90.0.3 20040415
$ gcc --version
gcc (GCC) 3.3.2
I attempted to build klibc with this toolchain. It builds without
errors, but the included "ash" shell does not function properly.
Testcase:
read cmdline </proc/cmdline
echo $cmdline
The first command prints a message:
cannot open /proc/cmdline: error 14
Other
2011 May 17
1
[PATCH] hivexregedit: Add --unsafe-printable-strings option.
This is a better way to make strings printable in the output
of hivexregedit / virt-win-reg.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
-------------- next part --------------
>From e16d1cc51c234eb9f3e7db3b8f77f76198ffee73 Mon
2010 Jan 14
0
[LLVMdev] Presenting Unsafe Math Flag to Optimizer
On Wed, Jan 13, 2010 at 4:20 PM, Bill Wendling <wendling at apple.com> wrote:
> Hi all,
>
> A quick question:
>
> The current implementation of the "allow unsafe math" option is to specify it via the TargetOptions object. However, this prevents the target-independent optimizer from using it. Are there any opinions (ha!) on how this could be achieved in a nice clean
2010 Jan 14
0
[LLVMdev] Presenting Unsafe Math Flag to Optimizer
Hi Bill,
> The current implementation of the "allow unsafe math" option is to specify it via the TargetOptions object. However, this prevents the target-independent optimizer from using it. Are there any opinions (ha!) on how this could be achieved in a nice clean manner which doesn't require using the TargetOptions object in the optimizer?
a flag on each floating point
2010 Jan 14
0
[LLVMdev] Presenting Unsafe Math Flag to Optimizer
> There are three options, that you mentioned off-line:
>
> A) Caller wins
> This could result in something the programmer didn't expect, possibly
> resulting in an incorrect answer.
>
> B) Don't inline
> We potentially miss important optimizations.
>
> C) Safety first
> The programmer could get code they didn't expect, but at least it won't
2011 Sep 26
0
[LLVMdev] [LLVMDev] The ComputeHash algorithm in FoldingSet is unsafe
I use FoldingSet to save some data structures. And I found somehow it always abandon a new node. I tracked the bug into the ComputeHash() function of FoldingSet. It computes the SAME hash value for these two 32-bit unsigned integer sequences:
size: 17
2012 Sep 13
0
[LLVMdev] unsafe math
I tried a simple float math (a + b - b) using llc's option
–enable-unsafe-fp-math, but I still have add and sub in the code
(x86).
Does LLVM perform any float/double reassociation, etc under unsafe
math or fast-math ?
Thanks
Junjie
2012 Sep 20
0
[LLVMdev] Handling of unsafe functions
On Wed, Sep 19, 2012 at 3:00 AM, Martinez, Javier E
<javier.e.martinez at intel.com> wrote:
> We have identified functions in LLVM sources using a static code analyzer
> which are marked as a “security vulnerability”[1][2]. There has been work
> already done to address some of them for Linux (e.g. snprintf). We are
> attempting to solve this issue in a comprehensive fashion
2013 Jul 26
0
[LLVMdev] [PROPOSAL] ELF safe/unsafe sections
On 26 July 2013 08:39, Rafael Espíndola <rafael.espindola at gmail.com> wrote:
> On 25 July 2013 17:24, Rui Ueyama <ruiu at google.com> wrote:
>> Then how about enable these flags for -O2? I want to hear from other people
>> cc'ed, and I may be too cautious, but I'd hesitate to define a new ELF
>> section if there's other mean already available to
2013 Jul 26
0
[LLVMdev] [PROPOSAL] ELF safe/unsafe sections
On 25 July 2013 17:24, Rui Ueyama <ruiu at google.com> wrote:
> Then how about enable these flags for -O2? I want to hear from other people
> cc'ed, and I may be too cautious, but I'd hesitate to define a new ELF
> section if there's other mean already available to achieve the same thing.
I would probably support doing that first. A small annoyance is that
the linker
2013 Jul 30
0
[LLVMdev] [PROPOSAL] ELF safe/unsafe sections
On Mon, Jul 29, 2013 at 9:24 AM, Nick Kledzik <kledzik at apple.com> wrote:
>
> On Jul 25, 2013, at 2:10 PM, Rui Ueyama wrote:
>> Is there any reason -ffunction-sections and -fdata-sections wouldn't work? If it'll work, it may be be better to say "if you want to get a better linker output use these options", rather than defining new ELF section.
>
> From
2002 Sep 24
0
[Bug 402] New: Suggested sshrc script unsafe
http://bugzilla.mindrot.org/show_bug.cgi?id=402
Summary: Suggested sshrc script unsafe
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P2
Component: Documentation
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: kolya at
2002 Sep 24
0
[Bug 402] Suggested sshrc script unsafe
http://bugzilla.mindrot.org/show_bug.cgi?id=402
todd at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From todd at openbsd.org 2002-09-25 07:04