b82e808b32
Merge pull request #156 from liblit/warning-fixes-unnecessary-code-uncontroversial
...
Fix 265 Eclipse warnings about unnecessary code
2017-03-23 17:48:10 -07:00
16492c7b78
Revert "Suppress 157 Eclipse warnings about unused exception parameters"
...
This reverts commit fe9f7a793a
2017-03-23 16:32:00 -05:00
9dafd5050f
Merge pull request #155 from liblit/warning-fixes-javadoc-true-fixes
...
Fix 161 Eclipse Javadoc warnings
2017-03-23 13:30:51 -07:00
e52d872e3e
Fix 19 Eclipse warnings about unnecessary casts
2017-03-23 12:28:14 -05:00
b8264b884d
Remove "@param" tags for which there is no corresponding parameter
2017-03-22 20:40:52 -05:00
780804e159
Fix "@param" tags whose name doesn't match the parameter name
2017-03-22 20:40:52 -05:00
7a198b0968
"@throws" with no other information is neither valid nor useful
2017-03-22 20:40:52 -05:00
17ee9c3f98
Fix assorted Javadoc typos, such as omitted "}"
2017-03-22 20:40:52 -05:00
323224504a
Suppress several unfixable warnings about unresolved type references
...
Fixing these Javadoc comments would require adding packages to various
other packages' build paths. In some of the cases suppressed,
changing build paths in that manner would create circular build
dependencies. In other cases, it would simply add a Javadoc-motivated
dependency that does not exist for the real code, which seems
undesirable. For a few cases, the reference seems to be to types in
code we don't even have here, such as code from "android" or
"org.mozilla" packages.
2017-03-22 20:40:52 -05:00
3b88836488
Fix broken type, field, and method references in Javadoc comments
2017-03-22 20:40:51 -05:00
9921fe37e6
Generalize a generic type parameter even more
...
As it turns out, I should have been using "? extends InstanceKey" rather
than "? super InstanceKey". But really, we can just use "?" here since
HeapGraph itself constrains its own type parameter appropriately.
2017-03-22 16:15:41 -05:00
2a33cb3649
Generalize an over-constrained generic parameter
...
This fixes WALA bug #151 , which was first introduced in commit fde6534
2017-03-22 14:16:54 -05:00
fe9f7a793a
Suppress 157 Eclipse warnings about unused exception parameters
...
In the cases addressed here, the caught exception is truly not needed
by the handling code.
2017-03-20 00:44:06 -05:00
6766f1e261
Fix 42 Eclipse warnings about unused imports
2017-03-20 00:43:48 -05:00
64f7751a00
Merge branch 'warning-fixes-potential-programming-problems'
2017-03-19 23:35:12 -05:00
a3f4c10c20
Merge pull request #150 from liblit/warning-fixes-potential-programming-problems
...
Resolve all Eclipse “Potential Programming Problem” warnings
2017-03-18 15:00:53 -07:00
421dcd4991
Change two "if" checks that can never be true into asserts
...
Eclipse warns that the "if" statements' true blocks are dead, and
indeed the conditions being tested here can never be true. It's a
little subtle why that's so, though. Changing them to "assert"
statements removes two warnings about deprecated code, while still
helping human readers understand what invariants must hold here.
2017-03-17 22:03:22 -05:00
296657a394
Suppress 88 Eclipse warnings about dead code
...
All of these involve conditionals that check some static, final debug
flag or debug level. The code will indeed be dead if WALA is built
with those debug facilities turned off. But we still want the code
present in case someone needs to turn some aspect of debugging on for
a while.
2017-03-17 21:49:34 -05:00
dfa8f15dac
Suppress two deprecation warnings about an internal CGNode API
...
The supposedly deprecated function (CGNode.addTarget) really seems to
be intended for internal use, not deprecated per se. We are an
internal user here, so presumably it's OK for us to be using this API
entry point.
2017-03-17 21:18:36 -05:00
811ce5257c
Merge pull request #145 from ponder-lab/IAnalysisCacheView
...
Additional refactorings for IAnalysisCacheView.
2017-03-15 13:18:12 -07:00
ab5aa90114
Suppress an Eclipse warning about unsafe varargs
...
Nothing we can do about this statically, due to Java limitations about
non-reifiable types.
2017-03-15 11:24:45 -05:00
c382934933
Fix an Eclipse warning about an unchecked cast
2017-03-15 11:24:40 -05:00
fde65340d2
Fix 132 Eclipse warnings about using raw generic types
2017-03-15 11:08:20 -05:00
d95b6e33f0
Merge remote-tracking branch 'origin/master' into IAnalysisCacheView
2017-03-14 17:24:19 -04:00
7e3066b6cd
bug 144
2017-03-14 10:05:18 -04:00
8fd41c148f
Use IAnalysisCacheView instead of AnalysisCache.
...
It seems that some additional types need to be changed due to
d24519e974
2017-03-13 16:27:05 -04:00
a1dd19b8d0
Merge branch 'pull-request__android-bugfixes' of https://github.com/joana-team/WALA
2017-03-11 16:56:09 -05:00
605e7373ce
Merge branch 'pull-request__exception-pruning-for-safe-array-creation' of https://github.com/joana-team/WALA
2017-03-11 16:38:03 -05:00
db65c16863
Merge branch 'pull-request__typeannotations' of https://github.com/joana-team/WALA
2017-03-11 16:19:50 -05:00
2a4d24dc6f
Merge branch 'pull-request__nullpointer-bugfixes' of https://github.com/joana-team/WALA
2017-03-11 14:48:13 -05:00
f595eb357e
add some abstraction to IR, using IRView
2017-03-11 13:22:45 -05:00
a1f8894ba1
Merge branch 'master' of https://github.com/wala/WALA
2017-03-10 13:49:09 -05:00
0545060886
merge
2017-03-10 13:49:07 -05:00
016c3940e8
Merge branch 'pull-request__misc-bugfixes' of https://github.com/joana-team/WALA
2017-03-09 08:59:40 -05:00
0784a9da6a
Merge pull request #124 from joana-team/slightly-more-informative-output
...
display which classes each handler catches when outputting IR
2017-03-09 08:51:06 -05:00
7b393a7da2
fix for missing Java 8 feature
2017-02-24 22:29:14 -05:00
96be295500
grr. commit -a does not find new files.
2017-02-02 20:46:34 -05:00
b65517b958
forgot some files
2017-02-02 20:44:27 -05:00
d24519e974
cross-cutting changes to make more of WALA runnable with TeaVM. The biggest change is refactoring to AnalysisCache and friends; since TeaVM does not support SoftReference, I needed to add a layer of interfaces so that I can use a more simpleminded caching implementation for TeaVM. There are other changes to Module and friends to break connections with File and URL, which also cause TeaVM grief. I also organized imports in many places to remove unused types that caused trouble.
2017-02-02 20:33:27 -05:00
64823846c0
get rid of HashCodeComparator and all its usages
...
This addresses both https://github.com/wala/WALA/issues/133 and
https://github.com/wala/WALA/issues/88
2017-01-26 14:16:48 +01:00
2396d0fad3
Revert "Revert "fixes to getting source positions from JVML""
...
This reverts commit 619df0a83d
2017-01-19 19:12:22 -05:00
619df0a83d
Revert "fixes to getting source positions from JVML"
...
This reverts commit 9e35099326
2017-01-19 18:49:02 -05:00
9e35099326
fixes to getting source positions from JVML
...
CAst rewriter abstraction
2017-01-19 17:52:42 -05:00
74cc8454e3
make more of WALA run on TeaVM
2017-01-17 13:14:56 -05:00
c9b1006305
changes for allowing seq. and conc. CHAs
2017-01-12 16:34:54 -05:00
602800524b
Hacks to make WALA run on TeaVM, and hence be able to run in Web browsers. TeaVM has some warts, but overall it is a very nice mechanism to run Java code on the browser. I have examples of analysis actually running in Firefox, which enables supportive tools. So, for those changes that are not ideal, such as dropping the ConcurrentHashMap in ClassHierarchy, we should find a way to support both them and TeaVM, based on demand.
2017-01-12 12:25:37 -05:00
37989efb6a
adapt to teavm changes
2017-01-03 21:06:21 -05:00
f42ad7aea6
Fix #127
...
Check that we only loop over the parameters actually being passed at
the call site in the SDG construction.
2017-01-02 15:36:38 -08:00
b9fb5e0481
display which classes each handler catches when outputting IR
2016-12-09 16:49:56 +01:00
4228bac5ff
If we see a call to an unknown method, conservatively add edges to all catch handlers
...
This is an attempt to fix issue #123
2016-12-09 16:46:01 +01:00
Manu Sridharan
Ben Liblit
Raffi Khatchadourian
Julian Dolby
Martin Mohr