[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #32053 [Applications/Tor Browser]: macOS bundles for Tor Browser 9.0a8 are not reproducible

#32053: macOS bundles for Tor Browser 9.0a8 are not reproducible
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  new
 Priority:  Immediate                            |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Critical                             |     Resolution:
 Keywords:  TorBrowserTeam201911, tbb-9.0-must,  |  Actual Points:
  tbb-9.0-issues, tbb-regression,                |
  tbb-9.0.1-can, GeorgKoppen201911               |
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by gk):

 Replying to [comment:12 gk]:
 > Replying to [comment:11 alexcrichton]:
 > > *.bc.z files in archives are a semi-custom compression format for LLVM
 IR files (we really should just use `*.gz`...) The `*.o` files are the
 codegen'd versions of those. Given that the LLVM IR is changing that means
 one of a few things:
 > >
 > > * Something in the source is changing, causing different IR to be
 produced
 > > * Rustc is non-deterministically producing IR
 > > * LLVM is non-deterministically optimizing IR

 While struggling with reducing libstyle size I got wondering whether there
 is a way to easily dzmp the output of those steps.  For instance, is there
 a rustc option i could use to dump the IR *before* LLVM is optimizing it
 so that we can narrow further down where the issue in the toolchain lies?
 I guess if we go the route you mentioned in comment:13 we would get the
 LLVM optimized IR? If not I'd be interested in dumping that as well with
 some compilation setting, if possible.

 If there aren't any such options to dump intermediate output yet, could
 you point me to the place in the compiler where I could hack this up?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32053#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs