This is an automated email from the git hooks/post-receive script.
unknown user pushed a change to branch users/aburgess/gdb-opt-code-debug in repository binutils-gdb.
discards e5a5ec2f4f3 [wip] Fix range end handling of inlined subroutines discards dffa48a83a6 [wip] Introduce a new line table flag is_weak discards 3a45541a3b3 [wip] gdb/testsuite: all the optimised code test cases discards f08bfa2b76a gdb: improve line number lookup around inline functions discards 397e5db80bf gdb: handle empty ranges for inline subroutines new bade3fecafb gdb: handle empty ranges for inline subroutines new 8a2fb168c9a gdb: improve line number lookup around inline functions new 94a13024343 [wip] gdb/testsuite: all the optimised code test cases new 215ba4f398c [wip] Introduce a new line table flag is_weak new cc9be6af06a [wip] Fix range end handling of inlined subroutines
This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:
* -- * -- B -- O -- O -- O (e5a5ec2f4f3) \ N -- N -- N refs/heads/users/aburgess/gdb-opt-code-debug (cc9be6af06a)
You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.
Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.
The 5 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.
Summary of changes: .../gdb.dwarf2/dw2-unexpected-entry-pc.exp | 30 ++++++++++++++-------- 1 file changed, 19 insertions(+), 11 deletions(-)