about summary refs log tree commit diff stats
path: root/015immediate_addressing.cc
Commit message (Collapse)AuthorAgeFilesLines
* 6090 - new instruction: multiply by immediateKartik Agaram2020-03-061-0/+39
| | | | | | | | | | | | | | | This is a 3-operand instruction: r32 = rm32 * imm32 It looks like https://c9x.me/x86/html/file_module_x86_id_138.html has a bug, implying the same opcode supports a 2-operand version. I don't see that in the Intel manual pdf, or at alternative sites like https://www.felixcloutier.com/x86/imul Native runs seem to validate my understanding. In the process I also fixed a bug in the existing multiply instruction 0f af: the only flags it sets are OF and CF. The other existing multiply instruction f7 was doing things right.
* 5983 - fix an emulator bounds-check bugKartik Agaram2020-02-051-1/+1
| | | | | | It was possible for an instruction to write out of bounds of the memory data structure. Most of the time this worked fine. However if the block ever got resized and moved the out-of-bounds bytes no longer went along.
* 5818Kartik Agaram2019-12-221-3/+3
|
* 5713Kartik Agaram2019-10-231-2/+2
|
* 5485 - promote SubX to top-levelKartik Agaram2019-07-271-0/+1272
class='oid'>f3ca75d6 ^
0f0659aa ^
f3ca75d6 ^

0f0659aa ^
f3ca75d6 ^

0f0659aa ^
f3ca75d6 ^

0f0659aa ^



f3ca75d6 ^

0f0659aa ^
f3ca75d6 ^

0f0659aa ^
f3ca75d6 ^

0f0659aa ^
f3ca75d6 ^

0f0659aa ^
f3ca75d6 ^

0f0659aa ^

f3ca75d6 ^


d4892b29 ^
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72










                                                                                                 
                                                       




                                                                                        
                                                                                                                  
                                                                                                                                   



                       





                                                     
                                         







                        
 
                                       

   
                             

   
                    

   



               

   
                              

   
                                                     

   
                                     

   
                            

   

                                                


                                                                         
                                                              
# Release Guide

Usually release candidates are tagged 0.6.0.rc1, 0.6.0.rc2 and tested for a week or so.

* Release libstrophe and libmesode if required

* Run Unit tests: `make check-unit`
* Run Functional tests - Currently disabled
* Run manual valgrind tests for new features
* Build and simple tests in Virtual machines ideally all dists including OSX and Windows (Cygwin)

* Update Inline command help (./src/command/cmd_defs.c)
* Check copright dates in all files (Copywright 2012-2019)

* Generate HTML docs (the docgen argument only works when package status is development)
    `./profanity docgen`

* Determine if libprofanitys version needs to be [increased](https://github.com/profanity-im/profanity/issues/973)
* Update plugin API docs (./apidocs/c and ./apidocs/python) need to run the `gen.sh` and commit the results to the website git repo
* Update CHANGELOG
* Update profrc.example

## Creating artefacts
* Set the correct release version in configure.ac:

```
AC_INIT([profanity], [0.6.0], [boothj5web@gmail.com])
```

* Set the package status in configure.ac:

```
PACKAGE_STATUS="release"
```

* Commit
* Tag (0.6.0)
* Push

* Configure to generate fresh Makefile:

```
./bootstrap.sh && ./configure
```

* Generate tarballs:

```
make dist
make dist-bzip2
make dist-xz
make dist-zip
```

* Set version to next release:

```
AC_INIT([profanity], [0.7.0], [boothj5web@gmail.com])
```

* Set the pacakge status back to dev:

```
PACKAGE_STATUS="development"
```

* Create a branch for patch releases (0.6.patch)
* Push

## Updating website
  * Make changes to the git repo incuding uploading the new artefacts at:
        https://github.com/profanity-im/profanity-im.github.io