diff options
author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2000-11-19 19:39:17 +0000 |
---|---|---|
committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2000-11-19 19:39:17 +0000 |
commit | 3248049694760f6520a3d2a4781c63c55173dccc (patch) | |
tree | e15fe308499975eeaa68413709286c001312ef05 /gcc/alias.c | |
parent | 9c31a032225cf5c0bb51f7c4ab1d6023df7d99d2 (diff) | |
download | gcc-3248049694760f6520a3d2a4781c63c55173dccc.tar.gz |
* alias.c (mems_in_disjoint_alias_sets_p): Do use alias sets in
stdarg and varargs functions.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@37572 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/alias.c')
-rw-r--r-- | gcc/alias.c | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/gcc/alias.c b/gcc/alias.c index e9e30ee8744..d89010aa72c 100644 --- a/gcc/alias.c +++ b/gcc/alias.c @@ -226,15 +226,6 @@ mems_in_disjoint_alias_sets_p (mem1, mem2) abort (); #endif - /* The code used in varargs macros are often not conforming ANSI C, - which can trick the compiler into making incorrect aliasing - assumptions in these functions. So, we don't use alias sets in - such a function. FIXME: This should be moved into the front-end; - it is a language-dependent notion, and there's no reason not to - still use these checks to handle globals. */ - if (current_function_stdarg || current_function_varargs) - return 0; - /* If have no alias set information for one of the MEMs, we have to assume it can alias anything. */ if (MEM_ALIAS_SET (mem1) == 0 || MEM_ALIAS_SET (mem2) == 0) |